Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3ef62a291a65d475f915979b7ab46e20a984f1870eb60fa4304dc3d0173acc8

Tx prefix hash: 6259b41d7a4bde893491c3b22b4bd2a543f1af6ccc1cd47a8941ee307358586f
Tx public key: d2e85904430ec600788b9594733e57b99b69cad57abaca0eaa7b923df97518e3
Timestamp: 1623955816 Timestamp [UCT]: 2021-06-17 18:50:16 Age [y:d:h:m:s]: 03:204:20:31:07
Block: 279434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 912823 RingCT/type: yes/0
Extra: 01d2e85904430ec600788b9594733e57b99b69cad57abaca0eaa7b923df97518e3021100000010ece3035d000000000000000000

1 output(s) for total of 72.798038832000 dcy

stealth address amount amount idx
00: d5d1b3dfcbe58d2c1e09efdbfac4f0d7bb69363cd66920d9abf17379ba653765 72.798038832000 585251 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": 279444, "vin": [ { "gen": { "height": 279434 } } ], "vout": [ { "amount": 72798038832, "target": { "key": "d5d1b3dfcbe58d2c1e09efdbfac4f0d7bb69363cd66920d9abf17379ba653765" } } ], "extra": [ 1, 210, 232, 89, 4, 67, 14, 198, 0, 120, 139, 149, 148, 115, 62, 87, 185, 155, 105, 202, 213, 122, 186, 202, 14, 170, 123, 146, 61, 249, 117, 24, 227, 2, 17, 0, 0, 0, 16, 236, 227, 3, 93, 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