Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d792823e50e518407887502ec8ecf5c9dbb58df44434623887b0626b6c29eb5f

Tx prefix hash: 99937b6cacd977021a10f901d3e41d98ac2ab582a1f6b41edb8a4189a5763b14
Tx public key: 217299c1986d68cf1824c2f9ec5516720ec6b6febb2a5e1bf26310ee959b27c1
Timestamp: 1750577065 Timestamp [UCT]: 2025-06-22 07:24:25 Age [y:d:h:m:s]: 00:141:00:07:32
Block: 1310306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98630 RingCT/type: yes/0
Extra: 01217299c1986d68cf1824c2f9ec5516720ec6b6febb2a5e1bf26310ee959b27c102110000000401491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3afd3e7c026026af8b31d109cb7aa7b8e87fb0e04831f9f0e5fea70ffe5a2ca2 0.600000000000 1797925 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": 1310316, "vin": [ { "gen": { "height": 1310306 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3afd3e7c026026af8b31d109cb7aa7b8e87fb0e04831f9f0e5fea70ffe5a2ca2" } } ], "extra": [ 1, 33, 114, 153, 193, 152, 109, 104, 207, 24, 36, 194, 249, 236, 85, 22, 114, 14, 198, 182, 254, 187, 42, 94, 27, 242, 99, 16, 238, 149, 155, 39, 193, 2, 17, 0, 0, 0, 4, 1, 73, 31, 136, 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