Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4b58e13e7edaa9d828290655da9faf2bb0f283bcc31758c1e777b616a42a0ef

Tx prefix hash: 0bd33bc71bf29742f299a7c13dcc059598ba682d6dcdb8c68eb580f6c94e2c5c
Tx public key: 294602aefab4fc58e1289e02ea75e668d8ae3dadc9d252663542bf8296133d7e
Timestamp: 1648220141 Timestamp [UCT]: 2022-03-25 14:55:41 Age [y:d:h:m:s]: 03:220:23:21:18
Block: 466153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 935831 RingCT/type: yes/0
Extra: 01294602aefab4fc58e1289e02ea75e668d8ae3dadc9d252663542bf8296133d7e02110000000a4a0f5013000000000000000000

1 output(s) for total of 17.516279111000 dcy

stealth address amount amount idx
00: 4b7ec91462e580f317bc71eefb0dcc20619a8bc69811084fc40e648a808ab037 17.516279111000 884410 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": 466163, "vin": [ { "gen": { "height": 466153 } } ], "vout": [ { "amount": 17516279111, "target": { "key": "4b7ec91462e580f317bc71eefb0dcc20619a8bc69811084fc40e648a808ab037" } } ], "extra": [ 1, 41, 70, 2, 174, 250, 180, 252, 88, 225, 40, 158, 2, 234, 117, 230, 104, 216, 174, 61, 173, 201, 210, 82, 102, 53, 66, 191, 130, 150, 19, 61, 126, 2, 17, 0, 0, 0, 10, 74, 15, 80, 19, 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