Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0d2b2e97c6ec318d603f61336a5ff12a50e417b8444f83002149bb146204214

Tx prefix hash: 408a8bf40e1e30a4f253d58dbf432a8797dcf1a0e27503e3ca891ce7328088bf
Tx public key: 9da696f193cf2d9db770ee6f4663585e75aa78a4fb4ff3b5fa085739d3074980
Timestamp: 1706058928 Timestamp [UCT]: 2024-01-24 01:15:28 Age [y:d:h:m:s]: 01:135:22:14:30
Block: 941944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358297 RingCT/type: yes/0
Extra: 019da696f193cf2d9db770ee6f4663585e75aa78a4fb4ff3b5fa085739d307498002110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b47f15a62c0c3983ef22ea80ac0960f774f00d8c09be27175d4bb7b80cdc24c5 0.600000000000 1400104 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": 941954, "vin": [ { "gen": { "height": 941944 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b47f15a62c0c3983ef22ea80ac0960f774f00d8c09be27175d4bb7b80cdc24c5" } } ], "extra": [ 1, 157, 166, 150, 241, 147, 207, 45, 157, 183, 112, 238, 111, 70, 99, 88, 94, 117, 170, 120, 164, 251, 79, 243, 181, 250, 8, 87, 57, 211, 7, 73, 128, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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