Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad41c690acbce03e2b41033c8ac2c9e411dd89182ee1cd5b1b2a6b0733d5eb82

Tx prefix hash: 410aa575e1deefa475fecec85f333fb7b4e3d401915ca905dd700f878fcbc84a
Tx public key: 2cd0ec77ffe9bd61d366dff5cee117e384522a85f70e373d3690fdfd2aefc601
Timestamp: 1719390475 Timestamp [UCT]: 2024-06-26 08:27:55 Age [y:d:h:m:s]: 01:136:23:09:44
Block: 1052497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356440 RingCT/type: yes/0
Extra: 012cd0ec77ffe9bd61d366dff5cee117e384522a85f70e373d3690fdfd2aefc6010211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: daf02a01130eaefab758f6bc35b9749d97c649bca1f58d6fc5f2dd5262752de0 0.600000000000 1522826 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": 1052507, "vin": [ { "gen": { "height": 1052497 } } ], "vout": [ { "amount": 600000000, "target": { "key": "daf02a01130eaefab758f6bc35b9749d97c649bca1f58d6fc5f2dd5262752de0" } } ], "extra": [ 1, 44, 208, 236, 119, 255, 233, 189, 97, 211, 102, 223, 245, 206, 225, 23, 227, 132, 82, 42, 133, 247, 14, 55, 61, 54, 144, 253, 253, 42, 239, 198, 1, 2, 17, 0, 0, 0, 3, 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