Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4eb35c755a222d11e43e5a76f4dde4ec404240ce2b54f40068e40f44a6b8be0

Tx prefix hash: f8d361d5c438e0c8ff2f18731a8be24b5f334d0483512db645fef6638fbdffcf
Tx public key: ec6b5750e944c53e24182f9f92354d4e9df92c22a846364df6a17d0fbd85a3d0
Timestamp: 1574563654 Timestamp [UCT]: 2019-11-24 02:47:34 Age [y:d:h:m:s]: 05:070:23:13:04
Block: 16108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1193359 RingCT/type: yes/0
Extra: 01ec6b5750e944c53e24182f9f92354d4e9df92c22a846364df6a17d0fbd85a3d0021100000008f95225a5000000000000000000

1 output(s) for total of 542.785692978000 dcy

stealth address amount amount idx
00: 0f2f9d1f253bd3e31581b3b2629bd3f01b509efb33b773526092040acd46c06b 542.785692978000 22292 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": 16118, "vin": [ { "gen": { "height": 16108 } } ], "vout": [ { "amount": 542785692978, "target": { "key": "0f2f9d1f253bd3e31581b3b2629bd3f01b509efb33b773526092040acd46c06b" } } ], "extra": [ 1, 236, 107, 87, 80, 233, 68, 197, 62, 36, 24, 47, 159, 146, 53, 77, 78, 157, 249, 44, 34, 168, 70, 54, 77, 246, 161, 125, 15, 189, 133, 163, 208, 2, 17, 0, 0, 0, 8, 249, 82, 37, 165, 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