Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f65585a8ccf65ee06d11f3f02a1096ff982c36579b73b5851331a40dba65583

Tx prefix hash: b15dd013d5da8082f0c1906bf4c328b98ec44a919f80e1d407f391f44b22006e
Tx public key: 708bd1810fa5c8fc7f0b43c9df307841b19b3c7e3d6bd808c862d37a4460654e
Timestamp: 1763840909 Timestamp [UCT]: 2025-11-22 19:48:29 Age [y:d:h:m:s]: 00:005:12:37:26
Block: 1417883 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3957 RingCT/type: yes/0
Extra: 01708bd1810fa5c8fc7f0b43c9df307841b19b3c7e3d6bd808c862d37a4460654e02110000001170609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61cb5603f18bb31004bbade033b95a8d2596163aa1a595b68df05a851ccba863 0.600000000000 1906410 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": 1417893, "vin": [ { "gen": { "height": 1417883 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61cb5603f18bb31004bbade033b95a8d2596163aa1a595b68df05a851ccba863" } } ], "extra": [ 1, 112, 139, 209, 129, 15, 165, 200, 252, 127, 11, 67, 201, 223, 48, 120, 65, 177, 155, 60, 126, 61, 107, 216, 8, 200, 98, 211, 122, 68, 96, 101, 78, 2, 17, 0, 0, 0, 17, 112, 96, 157, 3, 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