Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6706450aa3bd67fdc20314ff598db223c2a233c721b569d8fd4a5b670bf80c0f

Tx prefix hash: d5cc10bbd2c8ef2e95dfe83f04dd736dba458fd69180eca0d557755f34b80734
Tx public key: 4ab58e8ab553578ca22ef3d9ec6edbd3bd36f4e6bde80bba41a6ebdbb9fb4f1d
Timestamp: 1632466414 Timestamp [UCT]: 2021-09-24 06:53:34 Age [y:d:h:m:s]: 03:100:08:54:41
Block: 339853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 848114 RingCT/type: yes/0
Extra: 014ab58e8ab553578ca22ef3d9ec6edbd3bd36f4e6bde80bba41a6ebdbb9fb4f1d02110000000f5d7cc334000000000000000000

1 output(s) for total of 45.912016061000 dcy

stealth address amount amount idx
00: f5d802ce12434257dbc11afa8b0026d235b068f8bd693f1bfd4c94353254b770 45.912016061000 698788 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": 339863, "vin": [ { "gen": { "height": 339853 } } ], "vout": [ { "amount": 45912016061, "target": { "key": "f5d802ce12434257dbc11afa8b0026d235b068f8bd693f1bfd4c94353254b770" } } ], "extra": [ 1, 74, 181, 142, 138, 181, 83, 87, 140, 162, 46, 243, 217, 236, 110, 219, 211, 189, 54, 244, 230, 189, 232, 11, 186, 65, 166, 235, 219, 185, 251, 79, 29, 2, 17, 0, 0, 0, 15, 93, 124, 195, 52, 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