Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f6791022b50dcbeaffd0d97422bd25599c2b9fe79c28853cb934e9cd7f32bbb

Tx prefix hash: 9c1ac76525e2e12ff30458971c30d34c184599e10ecafa7f2c225f36e188b4d4
Tx public key: 60c45a7d87dd5d0150b6fa2bbe661f0468746658d5487e637d10a72c9f7a7916
Timestamp: 1705894933 Timestamp [UCT]: 2024-01-22 03:42:13 Age [y:d:h:m:s]: 01:145:03:16:54
Block: 940585 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364781 RingCT/type: yes/0
Extra: 0160c45a7d87dd5d0150b6fa2bbe661f0468746658d5487e637d10a72c9f7a791602110000002052d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 780e768a4dd8f7e71a6424d18d25c4d67b715f058e1ee3fadca4f5550a3ea110 0.600000000000 1398723 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": 940595, "vin": [ { "gen": { "height": 940585 } } ], "vout": [ { "amount": 600000000, "target": { "key": "780e768a4dd8f7e71a6424d18d25c4d67b715f058e1ee3fadca4f5550a3ea110" } } ], "extra": [ 1, 96, 196, 90, 125, 135, 221, 93, 1, 80, 182, 250, 43, 190, 102, 31, 4, 104, 116, 102, 88, 213, 72, 126, 99, 125, 16, 167, 44, 159, 122, 121, 22, 2, 17, 0, 0, 0, 32, 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