Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ad8faed54d58e0f5d11230fd96ae6c01ecd10eecedafa4f2be27d422e00f388

Tx prefix hash: a906a5f1a246dc05e61d3157e5643a610d454e73adc40f7489a4bac70c97517b
Tx public key: d7fdcf64189881ab44f864942ffecf9f4af84ca937974602cbf5bebfae7e4dd1
Timestamp: 1770259674 Timestamp [UTC]: 2026-02-05 02:47:54 Age [y:d:h:m:s]: 00:015:00:06:41
Block: 1470926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 10709 RingCT/type: yes/0
Extra: 01d7fdcf64189881ab44f864942ffecf9f4af84ca937974602cbf5bebfae7e4dd10208f12a6b8507a39432

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: caa0ff2a2bd700d01db4d5c43d66d3b4d9d5d35ea4f3d1af090ba643d60f7f5f 0.000600000000 1960196 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 dinastycoin-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": 1470936, "vin": [ { "gen": { "height": 1470926 } } ], "vout": [ { "amount": 600000000, "target": { "key": "caa0ff2a2bd700d01db4d5c43d66d3b4d9d5d35ea4f3d1af090ba643d60f7f5f" } } ], "extra": [ 1, 215, 253, 207, 100, 24, 152, 129, 171, 68, 248, 100, 148, 47, 254, 207, 159, 74, 248, 76, 169, 55, 151, 70, 2, 203, 245, 190, 191, 174, 126, 77, 209, 2, 8, 241, 42, 107, 133, 7, 163, 148, 50 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369