Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff14a25488e079e5511973a9df4d2aa2f8418d1be0ef9d4795bc49006cb72e66

Tx prefix hash: f606402c2de00771bc10242929e7f0eab43eaf17ae6527afebe7aa32336ca8a1
Tx public key: 84e564e2d937a00e4ee7a57c8693451b8d3582f77bc9af3b146f0fe5d5f50939
Timestamp: 1761229054 Timestamp [UCT]: 2025-10-23 14:17:34 Age [y:d:h:m:s]: 00:095:22:32:17
Block: 1396256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68498 RingCT/type: yes/0
Extra: 0184e564e2d937a00e4ee7a57c8693451b8d3582f77bc9af3b146f0fe5d5f50939021100000007e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d03f1d25a0533b7666d8f19c6d89224edc3b5cd39348b381d6861b236533e25e 0.600000000000 1884541 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": 1396266, "vin": [ { "gen": { "height": 1396256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d03f1d25a0533b7666d8f19c6d89224edc3b5cd39348b381d6861b236533e25e" } } ], "extra": [ 1, 132, 229, 100, 226, 217, 55, 160, 14, 78, 231, 165, 124, 134, 147, 69, 27, 141, 53, 130, 247, 123, 201, 175, 59, 20, 111, 15, 229, 213, 245, 9, 57, 2, 17, 0, 0, 0, 7, 228, 220, 144, 9, 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