Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39eadd14b493b4564a4fd8b3dba7e6ba11660196e8b8a3fd2426be98a78a2159

Tx prefix hash: ab9f22120c1bdbf9862bfc04770c8b4bb1652b5ce7e0502aec1bf0267f61e676
Tx public key: 9fcae860f46df05dc17d24d232276e5bce493d9292865f1381e173ac39493238
Timestamp: 1715341818 Timestamp [UCT]: 2024-05-10 11:50:18 Age [y:d:h:m:s]: 00:354:15:37:01
Block: 1018943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253517 RingCT/type: yes/0
Extra: 019fcae860f46df05dc17d24d232276e5bce493d9292865f1381e173ac394932380211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ddebc630f7099c0a254e6d8e444ffb50bf7306e87b6beaf2951f79c78abd83e 0.600000000000 1482768 of 15

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": 1018953, "vin": [ { "gen": { "height": 1018943 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ddebc630f7099c0a254e6d8e444ffb50bf7306e87b6beaf2951f79c78abd83e" } } ], "extra": [ 1, 159, 202, 232, 96, 244, 109, 240, 93, 193, 125, 36, 210, 50, 39, 110, 91, 206, 73, 61, 146, 146, 134, 95, 19, 129, 225, 115, 172, 57, 73, 50, 56, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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