Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed91a2d8f9e8b9256d3c366e2c4bfa65b414424908d55d86d884e23cd31db05a

Tx prefix hash: fe13bd0288f9ec2a4ffe658e5d049cc8412a333dd6dd09a437fc4f05c44ae7a6
Tx public key: e3e8eab73e364ca764e8c0d2ec2f03803780933152d166b073960906487e3a90
Timestamp: 1729825538 Timestamp [UCT]: 2024-10-25 03:05:38 Age [y:d:h:m:s]: 00:170:16:02:49
Block: 1138981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121782 RingCT/type: yes/0
Extra: 01e3e8eab73e364ca764e8c0d2ec2f03803780933152d166b073960906487e3a900211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 007a7293b320578e928b96a2b94069030eef8ea5cdba24c8c3af91f4f9299dcc 0.600000000000 1622728 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": 1138991, "vin": [ { "gen": { "height": 1138981 } } ], "vout": [ { "amount": 600000000, "target": { "key": "007a7293b320578e928b96a2b94069030eef8ea5cdba24c8c3af91f4f9299dcc" } } ], "extra": [ 1, 227, 232, 234, 183, 62, 54, 76, 167, 100, 232, 192, 210, 236, 47, 3, 128, 55, 128, 147, 49, 82, 209, 102, 176, 115, 150, 9, 6, 72, 126, 58, 144, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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