Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fab64dec09a851f9d68ea5f9894d11e91595110dde4b26a2e31e4b022029689f

Tx prefix hash: c3fe08e0934e6b091a25b6d94e1aebff112db5633860eceb2015ec6596386c8b
Tx public key: 133fdda1b4c17a37f52b2ea488e6fd19edc017111d105956ee1b486f87a38ecc
Timestamp: 1704292616 Timestamp [UCT]: 2024-01-03 14:36:56 Age [y:d:h:m:s]: 01:086:13:49:46
Block: 927348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322958 RingCT/type: yes/0
Extra: 01133fdda1b4c17a37f52b2ea488e6fd19edc017111d105956ee1b486f87a38ecc021100000006e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61f6bf7db084878b8f8beb54cdb5a84524b476dcb433af656526410077f6b902 0.600000000000 1385184 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": 927358, "vin": [ { "gen": { "height": 927348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61f6bf7db084878b8f8beb54cdb5a84524b476dcb433af656526410077f6b902" } } ], "extra": [ 1, 19, 63, 221, 161, 180, 193, 122, 55, 245, 43, 46, 164, 136, 230, 253, 25, 237, 192, 23, 17, 29, 16, 89, 86, 238, 27, 72, 111, 135, 163, 142, 204, 2, 17, 0, 0, 0, 6, 228, 187, 107, 131, 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