Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df2ee16957704502aeb7c1e3d544407ca5cca686629f946c539c2c60baf4a339

Tx prefix hash: 9affe0536dbb26e7c7950abd104741d5a150c63f161793e2c67c035c84150f69
Tx public key: 33dc4ccbd50f3febed1273d94337b4f64931e582cdb9cd19a03cca1fd4c3d39c
Timestamp: 1577929940 Timestamp [UCT]: 2020-01-02 01:52:20 Age [y:d:h:m:s]: 05:133:01:54:25
Block: 36814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1244943 RingCT/type: yes/0
Extra: 0133dc4ccbd50f3febed1273d94337b4f64931e582cdb9cd19a03cca1fd4c3d39c02110000000b4943cd9f000000000000000000

1 output(s) for total of 463.469103771000 dcy

stealth address amount amount idx
00: e1f579618d3740570b10504780af8485b806612dc17c113454fa792534cf031d 463.469103771000 62414 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": 36824, "vin": [ { "gen": { "height": 36814 } } ], "vout": [ { "amount": 463469103771, "target": { "key": "e1f579618d3740570b10504780af8485b806612dc17c113454fa792534cf031d" } } ], "extra": [ 1, 51, 220, 76, 203, 213, 15, 63, 235, 237, 18, 115, 217, 67, 55, 180, 246, 73, 49, 229, 130, 205, 185, 205, 25, 160, 60, 202, 31, 212, 195, 211, 156, 2, 17, 0, 0, 0, 11, 73, 67, 205, 159, 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