Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5f5f33745524e5de80e364aa759d7a820c93d82d7dfec3321abe5d76d67c9f7

Tx prefix hash: 3e3f6840355e5fcab19c8f4aca9ba41352995554e9a1f96c135c1f1275ad5657
Tx public key: 7840d66563f90bd526c54d8caee5d21b6d9f97ef79a747c7efdc6ae30c765dd7
Timestamp: 1732235759 Timestamp [UCT]: 2024-11-22 00:35:59 Age [y:d:h:m:s]: 00:002:06:58:07
Block: 1158904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1637 RingCT/type: yes/0
Extra: 017840d66563f90bd526c54d8caee5d21b6d9f97ef79a747c7efdc6ae30c765dd7021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d647fe4531efef993ffc8bd043d485575b7166d892bc0d185d898ed4b1197ad 0.600000000000 1644535 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": 1158914, "vin": [ { "gen": { "height": 1158904 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d647fe4531efef993ffc8bd043d485575b7166d892bc0d185d898ed4b1197ad" } } ], "extra": [ 1, 120, 64, 214, 101, 99, 249, 11, 213, 38, 197, 77, 140, 174, 229, 210, 27, 109, 159, 151, 239, 121, 167, 71, 199, 239, 220, 106, 227, 12, 118, 93, 215, 2, 17, 0, 0, 0, 9, 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