Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4193021b5e12e50a6b5d151c1923b693fa0cdcfe5b9748d3e0334efde217aab7

Tx prefix hash: e21dc3b6344859f42fb22d141c221f960595a7473357cd9c30ce7211c365fd46
Tx public key: f46bee435d11a1ff8f423ffac6c814e3c87acd28c5b1e47f7a435520ac85a6e9
Timestamp: 1764244343 Timestamp [UCT]: 2025-11-27 11:52:23 Age [y:d:h:m:s]: 00:007:03:14:03
Block: 1421246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5115 RingCT/type: yes/0
Extra: 01f46bee435d11a1ff8f423ffac6c814e3c87acd28c5b1e47f7a435520ac85a6e902110000000dd6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 833c0d104d945572ab7b90f9185fe4a1cf1609a15548790cf6b198398baf37c6 0.600000000000 1909803 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": 1421256, "vin": [ { "gen": { "height": 1421246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "833c0d104d945572ab7b90f9185fe4a1cf1609a15548790cf6b198398baf37c6" } } ], "extra": [ 1, 244, 107, 238, 67, 93, 17, 161, 255, 143, 66, 63, 250, 198, 200, 20, 227, 200, 122, 205, 40, 197, 177, 228, 127, 122, 67, 85, 32, 172, 133, 166, 233, 2, 17, 0, 0, 0, 13, 214, 225, 157, 124, 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