Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8d915b6a9a3ade893fb31e477e68947d9b2644d13a705f3a71dcb7f623d6d4b

Tx prefix hash: d51d42295e60f9d034374dde774f372fa03afeb173645e67253a7a4d09dbadc0
Tx public key: edb6b7317c7da0fcf95ce7c024ad3370d42c7ccf900c50133d5d9e755dfe55b4
Timestamp: 1578944013 Timestamp [UCT]: 2020-01-13 19:33:33 Age [y:d:h:m:s]: 05:269:21:30:27
Block: 44921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1340660 RingCT/type: yes/0
Extra: 01edb6b7317c7da0fcf95ce7c024ad3370d42c7ccf900c50133d5d9e755dfe55b4021100000004d81c26c0000000000000000000

1 output(s) for total of 435.671268152000 dcy

stealth address amount amount idx
00: 66c72032db4fee3edf0518fecbcc81b4b21d09280aaa4ab11e44dc863d7bd9ce 435.671268152000 81902 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": 44931, "vin": [ { "gen": { "height": 44921 } } ], "vout": [ { "amount": 435671268152, "target": { "key": "66c72032db4fee3edf0518fecbcc81b4b21d09280aaa4ab11e44dc863d7bd9ce" } } ], "extra": [ 1, 237, 182, 183, 49, 124, 125, 160, 252, 249, 92, 231, 192, 36, 173, 51, 112, 212, 44, 124, 207, 144, 12, 80, 19, 61, 93, 158, 117, 93, 254, 85, 180, 2, 17, 0, 0, 0, 4, 216, 28, 38, 192, 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