Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3aac7a39e416fcb97d6c700bdc1348794906ebd1d7e37f6901eaf75857a849f9

Tx prefix hash: 774566e8f61dc7c87c282d200d2cd190b5de5d45321bc75fc5edaddba9f0a5d3
Tx public key: 0b37989c538cb3ec98456d462ab1f92829acde29a0db16dbff17f1fa0f11e4fa
Timestamp: 1707192423 Timestamp [UCT]: 2024-02-06 04:07:03 Age [y:d:h:m:s]: 01:282:05:27:21
Block: 951364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 460497 RingCT/type: yes/0
Extra: 010b37989c538cb3ec98456d462ab1f92829acde29a0db16dbff17f1fa0f11e4fa02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 580b85c724ca1e056988d335a7e0c91e446a16e40cd19e540b6d8141b3602dd4 0.600000000000 1410118 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": 951374, "vin": [ { "gen": { "height": 951364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "580b85c724ca1e056988d335a7e0c91e446a16e40cd19e540b6d8141b3602dd4" } } ], "extra": [ 1, 11, 55, 152, 156, 83, 140, 179, 236, 152, 69, 109, 70, 42, 177, 249, 40, 41, 172, 222, 41, 160, 219, 22, 219, 255, 23, 241, 250, 15, 17, 228, 250, 2, 17, 0, 0, 0, 3, 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