Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9121000f97521de634e8a685662de318a12e9df64c916ecb266fc8ad4350bc3

Tx prefix hash: ec1409a7d53af9b3fca3813d39043c5c3a1c67127984ef9341279f569b907ce2
Tx public key: db3f8bb705d01bfe5e9cc0d2cafe6f87f6e7c247038ed0f897da0c1eee54691b
Timestamp: 1716585386 Timestamp [UCT]: 2024-05-24 21:16:26 Age [y:d:h:m:s]: 00:276:12:29:45
Block: 1029250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197600 RingCT/type: yes/0
Extra: 01db3f8bb705d01bfe5e9cc0d2cafe6f87f6e7c247038ed0f897da0c1eee54691b0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cd118c47a08cf9923fc013997613703fbbbe6526c4189e520f13b8e860f039d 0.600000000000 1497289 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": 1029260, "vin": [ { "gen": { "height": 1029250 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cd118c47a08cf9923fc013997613703fbbbe6526c4189e520f13b8e860f039d" } } ], "extra": [ 1, 219, 63, 139, 183, 5, 208, 27, 254, 94, 156, 192, 210, 202, 254, 111, 135, 246, 231, 194, 71, 3, 142, 208, 248, 151, 218, 12, 30, 238, 84, 105, 27, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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