Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8d0107a583025cf1f6be607dae44111fc7909d6dedb5bef54a1593ca6436d5d

Tx prefix hash: dbd858eebfe39c1be34c2780662f1970616884714395e29427fdc55b92251d6c
Tx public key: 73ca55c02ea50d092dca5f6376c31e83f4776fd96ab6fb28ee583c6b3071f4e9
Timestamp: 1730145094 Timestamp [UCT]: 2024-10-28 19:51:34 Age [y:d:h:m:s]: 00:230:21:06:15
Block: 1141592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164786 RingCT/type: yes/0
Extra: 0173ca55c02ea50d092dca5f6376c31e83f4776fd96ab6fb28ee583c6b3071f4e90211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 632b0b67643872925f98e9b96e1ed76878ae5a7a39efcfc80116692977f1750d 0.600000000000 1625401 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": 1141602, "vin": [ { "gen": { "height": 1141592 } } ], "vout": [ { "amount": 600000000, "target": { "key": "632b0b67643872925f98e9b96e1ed76878ae5a7a39efcfc80116692977f1750d" } } ], "extra": [ 1, 115, 202, 85, 192, 46, 165, 13, 9, 45, 202, 95, 99, 118, 195, 30, 131, 244, 119, 111, 217, 106, 182, 251, 40, 238, 88, 60, 107, 48, 113, 244, 233, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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