Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3663429246cf05bc47933b9721e2d6955aaf77c9cf97c8a4c17406a58b0565d7

Tx prefix hash: 3e669080f6697814efb35e9bcf7fe9cb14e264a86ddef0a3d9319a82ff625cf5
Tx public key: 931186c733f74f0a2655d387fef23eadd12630717f808883d9019045c8adb160
Timestamp: 1704797766 Timestamp [UCT]: 2024-01-09 10:56:06 Age [y:d:h:m:s]: 01:158:22:52:19
Block: 931508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374652 RingCT/type: yes/0
Extra: 01931186c733f74f0a2655d387fef23eadd12630717f808883d9019045c8adb1600211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2b9cb51e49d22cd5296a0e2ba6d22e4ae6d15edbaae9c24a7e12006be109fb3 0.600000000000 1389410 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": 931518, "vin": [ { "gen": { "height": 931508 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2b9cb51e49d22cd5296a0e2ba6d22e4ae6d15edbaae9c24a7e12006be109fb3" } } ], "extra": [ 1, 147, 17, 134, 199, 51, 247, 79, 10, 38, 85, 211, 135, 254, 242, 62, 173, 209, 38, 48, 113, 127, 128, 136, 131, 217, 1, 144, 69, 200, 173, 177, 96, 2, 17, 0, 0, 0, 4, 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