Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ffc261a27872f247b2602cbe5342e408caf6169e57a242386dd0f3280b3a788

Tx prefix hash: ae7a95e4fe61ec7c3f090bb9087fc393b921df0080ce3a062a4ddade438d277d
Tx public key: bc7941d168acd77bc7ec5d96b9fb8997a256e1af5cb41d6171ec0a7be3f8254c
Timestamp: 1737534739 Timestamp [UCT]: 2025-01-22 08:32:19 Age [y:d:h:m:s]: 00:146:07:59:33
Block: 1202732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104333 RingCT/type: yes/0
Extra: 01bc7941d168acd77bc7ec5d96b9fb8997a256e1af5cb41d6171ec0a7be3f8254c0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb52b358ebde1f015b0a16403e417e9af6b7c0eedcc291ad330b24ef2579aa03 0.600000000000 1689397 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": 1202742, "vin": [ { "gen": { "height": 1202732 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb52b358ebde1f015b0a16403e417e9af6b7c0eedcc291ad330b24ef2579aa03" } } ], "extra": [ 1, 188, 121, 65, 209, 104, 172, 215, 123, 199, 236, 93, 150, 185, 251, 137, 151, 162, 86, 225, 175, 92, 180, 29, 97, 113, 236, 10, 123, 227, 248, 37, 76, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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