Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5dfd45c2cda5f76280beb74b453f21ab4e9f52c1d53d27868137b29c76fef9e

Tx prefix hash: 776b450008c548cb562e741d1a2c712c6a8298b44e56937203cf5d3187d0014d
Tx public key: 97a4251a50518080b30a5b67e3f1c2b121245107cc6723b720fd4343a09420a1
Timestamp: 1702751939 Timestamp [UCT]: 2023-12-16 18:38:59 Age [y:d:h:m:s]: 01:103:14:13:57
Block: 914562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335165 RingCT/type: yes/0
Extra: 0197a4251a50518080b30a5b67e3f1c2b121245107cc6723b720fd4343a09420a102110000000233af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf30ee8c5cd87e8f45d1e25bbdf46b18c4816fcdd4dae726013a9aebddd854f5 0.600000000000 1371892 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": 914572, "vin": [ { "gen": { "height": 914562 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf30ee8c5cd87e8f45d1e25bbdf46b18c4816fcdd4dae726013a9aebddd854f5" } } ], "extra": [ 1, 151, 164, 37, 26, 80, 81, 128, 128, 179, 10, 91, 103, 227, 241, 194, 177, 33, 36, 81, 7, 204, 103, 35, 183, 32, 253, 67, 67, 160, 148, 32, 161, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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