Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 21fadbfeb958cfd8841759e09f6978d90fa78f8d873f796621b131df5756fb59

Tx prefix hash: 77c6be2ae7f5ba74c57594ff6b1636254ff7093ed7d65516c310450aa80c4b61
Tx public key: 6f3111723acc49f3af58a30851f595753d40dc1b0610dbff5ba950a32627ac22
Timestamp: 1583240556 Timestamp [UCT]: 2020-03-03 13:02:36 Age [y:d:h:m:s]: 04:297:13:51:10
Block: 75846 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106747 RingCT/type: yes/0
Extra: 016f3111723acc49f3af58a30851f595753d40dc1b0610dbff5ba950a32627ac220211000000144943cd9f000000000000000000

1 output(s) for total of 344.105419698000 dcy

stealth address amount amount idx
00: e0cdda5816827fb8ba6fb739fc1a952851b5ccb11408f6e4c54ad6b2ddaf62b1 344.105419698000 139825 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 75856, "vin": [ { "gen": { "height": 75846 } } ], "vout": [ { "amount": 344105419698, "target": { "key": "e0cdda5816827fb8ba6fb739fc1a952851b5ccb11408f6e4c54ad6b2ddaf62b1" } } ], "extra": [ 1, 111, 49, 17, 114, 58, 204, 73, 243, 175, 88, 163, 8, 81, 245, 149, 117, 61, 64, 220, 27, 6, 16, 219, 255, 91, 169, 80, 163, 38, 39, 172, 34, 2, 17, 0, 0, 0, 20, 73, 67, 205, 159, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8