Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5395576759fefd90b73a8b243db30044e41a62660a3aa542641af0ca45036727

Tx prefix hash: 9982df12abd48a9fcb797ddfcac035285af5762fe521e6ca174d3bf40a180c33
Tx public key: 0a9ea2b55c31dd3c860e00a8b25d1fbfa9521d452a8bce5866d2a77a3c0e682c
Timestamp: 1729479228 Timestamp [UCT]: 2024-10-21 02:53:48 Age [y:d:h:m:s]: 00:171:15:09:50
Block: 1136101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122482 RingCT/type: yes/0
Extra: 010a9ea2b55c31dd3c860e00a8b25d1fbfa9521d452a8bce5866d2a77a3c0e682c021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d8860a74fb2f156823001ece2eecbe257967e60ed728ce1da7996ad20204cdb 0.600000000000 1619444 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": 1136111, "vin": [ { "gen": { "height": 1136101 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d8860a74fb2f156823001ece2eecbe257967e60ed728ce1da7996ad20204cdb" } } ], "extra": [ 1, 10, 158, 162, 181, 92, 49, 221, 60, 134, 14, 0, 168, 178, 93, 31, 191, 169, 82, 29, 69, 42, 139, 206, 88, 102, 210, 167, 122, 60, 14, 104, 44, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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