Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0fb9f96b4cd894c98f36c1932b663edd40aa9681385dadcf6eb0edca35868a0

Tx prefix hash: afc2960d96982a126ca0d71cd1f466fb9b2ad0225711cb22b75780c5042e81b4
Tx public key: 68475e9f9b35f0bcf634b9dcc22aa49f3e5437ffb23f11b92eacb14d74fa55ec
Timestamp: 1751015222 Timestamp [UCT]: 2025-06-27 09:07:02 Age [y:d:h:m:s]: 00:142:21:33:10
Block: 1313768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100151 RingCT/type: yes/0
Extra: 0168475e9f9b35f0bcf634b9dcc22aa49f3e5437ffb23f11b92eacb14d74fa55ec021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa98194e7cb1d2656c3cf99db86b20ecc0f231272425613ce8b3c8cb654d5f00 0.600000000000 1801411 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": 1313778, "vin": [ { "gen": { "height": 1313768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa98194e7cb1d2656c3cf99db86b20ecc0f231272425613ce8b3c8cb654d5f00" } } ], "extra": [ 1, 104, 71, 94, 159, 155, 53, 240, 188, 246, 52, 185, 220, 194, 42, 164, 159, 62, 84, 55, 255, 178, 63, 17, 185, 46, 172, 177, 77, 116, 250, 85, 236, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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