Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b941c99438ea6e7243656c238772e68f111b8b850148bc2ef84dc89b66d83063

Tx prefix hash: 84ee68486886ed263b5f39932edf334aa9f61b5ca7d4774cd5dabc5577d33900
Tx public key: 80a8ef5a79e4e45733b38947fc40d5bb17f9715f8d70d3d2209d6e00ea051934
Timestamp: 1710649933 Timestamp [UCT]: 2024-03-17 04:32:13 Age [y:d:h:m:s]: 01:004:20:38:52
Block: 980054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264441 RingCT/type: yes/0
Extra: 0180a8ef5a79e4e45733b38947fc40d5bb17f9715f8d70d3d2209d6e00ea05193402110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61c218c0478add434627893c7c636b933ed47c22072d903c0c992532ac6a1dfe 0.600000000000 1440113 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": 980064, "vin": [ { "gen": { "height": 980054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61c218c0478add434627893c7c636b933ed47c22072d903c0c992532ac6a1dfe" } } ], "extra": [ 1, 128, 168, 239, 90, 121, 228, 228, 87, 51, 179, 137, 71, 252, 64, 213, 187, 23, 249, 113, 95, 141, 112, 211, 210, 32, 157, 110, 0, 234, 5, 25, 52, 2, 17, 0, 0, 0, 8, 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