Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7becd4932bd3ab1a74cd2d1cc65d3005db1c8cb208f8e7744dab866e9284d3a

Tx prefix hash: 26ec4cacd0f3bcd2db4bb179ad9805325baf99561f55f8552953f8f03c2a17e0
Tx public key: aac94f47ecf8cfa83e253795dfe9b13a668550ae5b3d173609a17b6e1f6385c5
Timestamp: 1712110264 Timestamp [UCT]: 2024-04-03 02:11:04 Age [y:d:h:m:s]: 00:226:08:37:32
Block: 992114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162082 RingCT/type: yes/0
Extra: 01aac94f47ecf8cfa83e253795dfe9b13a668550ae5b3d173609a17b6e1f6385c50211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 515bc0f5ab080f01b777afda6e68e044b1be33f28ed7bc1ff53637e5ea9327e4 0.600000000000 1452450 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": 992124, "vin": [ { "gen": { "height": 992114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "515bc0f5ab080f01b777afda6e68e044b1be33f28ed7bc1ff53637e5ea9327e4" } } ], "extra": [ 1, 170, 201, 79, 71, 236, 248, 207, 168, 62, 37, 55, 149, 223, 233, 177, 58, 102, 133, 80, 174, 91, 61, 23, 54, 9, 161, 123, 110, 31, 99, 133, 197, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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