Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfdcd3232581ebe17b09dd376fb1e5f6dea5f31bc693d279bf27c78041648a48

Tx prefix hash: f4be38ce4573c6a1f0aaace2e1553fb934aaf534653d06d2f94f6ff95a07fa2c
Tx public key: f2dc8b120a99faef0e5c514009da6a3a80582bdaa45fae647e4d6c6494600553
Timestamp: 1751132466 Timestamp [UCT]: 2025-06-28 17:41:06 Age [y:d:h:m:s]: 00:143:15:57:11
Block: 1314672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100760 RingCT/type: yes/0
Extra: 01f2dc8b120a99faef0e5c514009da6a3a80582bdaa45fae647e4d6c649460055302110000000743846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4be0320ade074a7bf5651b6988de2fd46516cfdb03fd8ca7dc0076e96d2dc0c3 0.600000000000 1802323 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": 1314682, "vin": [ { "gen": { "height": 1314672 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4be0320ade074a7bf5651b6988de2fd46516cfdb03fd8ca7dc0076e96d2dc0c3" } } ], "extra": [ 1, 242, 220, 139, 18, 10, 153, 250, 239, 14, 92, 81, 64, 9, 218, 106, 58, 128, 88, 43, 218, 164, 95, 174, 100, 126, 77, 108, 100, 148, 96, 5, 83, 2, 17, 0, 0, 0, 7, 67, 132, 109, 102, 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