Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fb5f2cb00519be4e393772c6a637f218f334c6c9745388acaf26be6917273fc

Tx prefix hash: f6f8126991298a2fb2daa20e43ef6ed2fe58e051564e09e3c52c9834a6564888
Tx public key: adc79d9462477bacfeb8e0cbaa46d28d10e7a4d98c3bfff8382be7629f3c1893
Timestamp: 1744651444 Timestamp [UCT]: 2025-04-14 17:24:04 Age [y:d:h:m:s]: 00:271:03:04:23
Block: 1261425 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191583 RingCT/type: yes/0
Extra: 01adc79d9462477bacfeb8e0cbaa46d28d10e7a4d98c3bfff8382be7629f3c1893021100000009dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef3ad6b41afb0be48b2e47091ad708bb05e13ac035d2a1c5ff7b86fdb14590f3 0.600000000000 1748594 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": 1261435, "vin": [ { "gen": { "height": 1261425 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef3ad6b41afb0be48b2e47091ad708bb05e13ac035d2a1c5ff7b86fdb14590f3" } } ], "extra": [ 1, 173, 199, 157, 148, 98, 71, 123, 172, 254, 184, 224, 203, 170, 70, 210, 141, 16, 231, 164, 217, 140, 59, 255, 248, 56, 43, 231, 98, 159, 60, 24, 147, 2, 17, 0, 0, 0, 9, 219, 181, 113, 193, 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