Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c272571b451f92e6bf499c0c63394b19e68741ea9e2b5ec14c304f4ef7d62be3

Tx prefix hash: af4578e0d084b73fd8a04395d0970dfc514dd49dee4db37eb0ccb197d4e513ba
Tx public key: 14db2b2f6735bf8d66a61af30911260f85afc81776bece3c15a73c1cd7febee4
Timestamp: 1764928280 Timestamp [UCT]: 2025-12-05 09:51:20 Age [y:d:h:m:s]: 00:016:18:19:25
Block: 1426915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11986 RingCT/type: yes/0
Extra: 0114db2b2f6735bf8d66a61af30911260f85afc81776bece3c15a73c1cd7febee4021100000002d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 734b7da80a52d63f9633d3120cfa05931395389888c2fe6d3cd3536e3a631745 0.600000000000 1915610 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": 1426925, "vin": [ { "gen": { "height": 1426915 } } ], "vout": [ { "amount": 600000000, "target": { "key": "734b7da80a52d63f9633d3120cfa05931395389888c2fe6d3cd3536e3a631745" } } ], "extra": [ 1, 20, 219, 43, 47, 103, 53, 191, 141, 102, 166, 26, 243, 9, 17, 38, 15, 133, 175, 200, 23, 118, 190, 206, 60, 21, 167, 60, 28, 215, 254, 190, 228, 2, 17, 0, 0, 0, 2, 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