Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c88d18b3d18cce5e0a047ffc23a2c848daf5d5aeae99a2d62dc74d057440849f

Tx prefix hash: c59ecaba49070882aee7721b0f8b14bc591ab97483b07add98e3cb2703474077
Tx public key: 275bf21dc9c596edef1d6d8fdb781b4b450c7548a095686410618a7a72fe5b43
Timestamp: 1761176989 Timestamp [UCT]: 2025-10-22 23:49:49 Age [y:d:h:m:s]: 00:035:08:44:38
Block: 1395824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25316 RingCT/type: yes/0
Extra: 01275bf21dc9c596edef1d6d8fdb781b4b450c7548a095686410618a7a72fe5b4302110000000901491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf3fb628673c77ed3f0c395fcd727f4a4e0090377b192d8a6ed31a6356af3bba 0.600000000000 1884107 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": 1395834, "vin": [ { "gen": { "height": 1395824 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf3fb628673c77ed3f0c395fcd727f4a4e0090377b192d8a6ed31a6356af3bba" } } ], "extra": [ 1, 39, 91, 242, 29, 201, 197, 150, 237, 239, 29, 109, 143, 219, 120, 27, 75, 69, 12, 117, 72, 160, 149, 104, 100, 16, 97, 138, 122, 114, 254, 91, 67, 2, 17, 0, 0, 0, 9, 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