Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 546549436264e170a39517d9641366763712a4d55b814b72bffe1511f28476f5

Tx prefix hash: 9e355b547e605ad52c46f0d844289e67406a2d35be9329afe0662359f4744e6c
Tx public key: 6905b9ca71a9c1a459b40f9e1fdf992a8a0a03ee941eb2c49a70eee80924aef2
Timestamp: 1705549670 Timestamp [UCT]: 2024-01-18 03:47:50 Age [y:d:h:m:s]: 01:091:13:59:14
Block: 937725 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326577 RingCT/type: yes/0
Extra: 016905b9ca71a9c1a459b40f9e1fdf992a8a0a03ee941eb2c49a70eee80924aef20211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d90ba7041fc740d57b1515c3af06ffefab2be5f392fe6bae07c62a35cb0e9bdc 0.600000000000 1395787 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": 937735, "vin": [ { "gen": { "height": 937725 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d90ba7041fc740d57b1515c3af06ffefab2be5f392fe6bae07c62a35cb0e9bdc" } } ], "extra": [ 1, 105, 5, 185, 202, 113, 169, 193, 164, 89, 180, 15, 158, 31, 223, 153, 42, 138, 10, 3, 238, 148, 30, 178, 196, 154, 112, 238, 232, 9, 36, 174, 242, 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