Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3dd899deb60bf7c7d8a5040cc0325b0afdae1900cfb39bd5a56e06e5df9c0cdb

Tx prefix hash: e9bb9df733d83918ed3ca34946a0bd4dd801b4afd5cee6118fabb360e7838333
Tx public key: e3efdca97e77c17de4ca067f5d362610e422989be1c7313dcb58377a6fc817ca
Timestamp: 1706372755 Timestamp [UCT]: 2024-01-27 16:25:55 Age [y:d:h:m:s]: 01:069:01:15:58
Block: 944558 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310438 RingCT/type: yes/0
Extra: 01e3efdca97e77c17de4ca067f5d362610e422989be1c7313dcb58377a6fc817ca02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53ee0f790396185adf3b09de302802449d68fedfdc360a07de9a8f6e6c1f6614 0.600000000000 1402836 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": 944568, "vin": [ { "gen": { "height": 944558 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53ee0f790396185adf3b09de302802449d68fedfdc360a07de9a8f6e6c1f6614" } } ], "extra": [ 1, 227, 239, 220, 169, 126, 119, 193, 125, 228, 202, 6, 127, 93, 54, 38, 16, 228, 34, 152, 155, 225, 199, 49, 61, 203, 88, 55, 122, 111, 200, 23, 202, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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