Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4e7071f5037b102808efec292af380b4acc47f5c4daedea2887c5dee3acea95

Tx prefix hash: b851b9b7cd1ea136c60329723e06e801333ce66640bb3fb07220a19106a3f7b1
Tx public key: 682af1ba35a014dc3a4a382c8fe8d06135f91fada2d547b0251bde94ef4f0b79
Timestamp: 1723267778 Timestamp [UCT]: 2024-08-10 05:29:38 Age [y:d:h:m:s]: 00:242:16:56:05
Block: 1084648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173342 RingCT/type: yes/0
Extra: 01682af1ba35a014dc3a4a382c8fe8d06135f91fada2d547b0251bde94ef4f0b79021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39573200b430503a09aaf4bf6509d7b9003d90a262f2a13d7d3ded2c8f9be3a8 0.600000000000 1559001 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": 1084658, "vin": [ { "gen": { "height": 1084648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39573200b430503a09aaf4bf6509d7b9003d90a262f2a13d7d3ded2c8f9be3a8" } } ], "extra": [ 1, 104, 42, 241, 186, 53, 160, 20, 220, 58, 74, 56, 44, 143, 232, 208, 97, 53, 249, 31, 173, 162, 213, 71, 176, 37, 27, 222, 148, 239, 79, 11, 121, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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