Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4d4e9dbddeaee1f901b714affd11134117e76745a33bc12162b2ad5a8d685e0

Tx prefix hash: 4baca3e15c5aac64daf4754146be212d5fc795ff0a56e1e8ecd9211db4de4748
Tx public key: 2a2daa2a2512cb9f53b63ab36bb99fb7c8faf160c1136b4d72cba208018df4a8
Timestamp: 1711708289 Timestamp [UCT]: 2024-03-29 10:31:29 Age [y:d:h:m:s]: 01:226:09:18:28
Block: 988832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 420467 RingCT/type: yes/0
Extra: 012a2daa2a2512cb9f53b63ab36bb99fb7c8faf160c1136b4d72cba208018df4a802110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9dacc99b97e2f419507d414fad17c8edea16ae474bef94e70245ae62010b7237 0.600000000000 1449117 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": 988842, "vin": [ { "gen": { "height": 988832 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9dacc99b97e2f419507d414fad17c8edea16ae474bef94e70245ae62010b7237" } } ], "extra": [ 1, 42, 45, 170, 42, 37, 18, 203, 159, 83, 182, 58, 179, 107, 185, 159, 183, 200, 250, 241, 96, 193, 19, 107, 77, 114, 203, 162, 8, 1, 141, 244, 168, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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