Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97e80e4709e245ce2bfc14d8028a4743d1882efbc78f4be275d1a88a0cb809b3

Tx prefix hash: 6448c1733412fe4f91232f6b9f944169ca65f9bed18f85fda4c5680742a3b8b6
Tx public key: be6d5f8a01f12f97be8a14f3c13da23f8baafb15e05a42e8021634ca5ffda31a
Timestamp: 1762198743 Timestamp [UCT]: 2025-11-03 19:39:03 Age [y:d:h:m:s]: 00:065:18:52:55
Block: 1404279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47116 RingCT/type: yes/0
Extra: 01be6d5f8a01f12f97be8a14f3c13da23f8baafb15e05a42e8021634ca5ffda31a0211000000035dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f8d97d2cdeca7a5588780ec570276444503659eaa83996faa324d2f0a1ac5ac 0.600000000000 1892636 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": 1404289, "vin": [ { "gen": { "height": 1404279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f8d97d2cdeca7a5588780ec570276444503659eaa83996faa324d2f0a1ac5ac" } } ], "extra": [ 1, 190, 109, 95, 138, 1, 241, 47, 151, 190, 138, 20, 243, 193, 61, 162, 63, 139, 170, 251, 21, 224, 90, 66, 232, 2, 22, 52, 202, 95, 253, 163, 26, 2, 17, 0, 0, 0, 3, 93, 251, 190, 42, 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