Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be4cdd3f303cd4534a9a2bc8a4b3ea331b073bf3d0819fc929406b4a10c72cf6

Tx prefix hash: c72751347109aa4d3b8f6e0aa070d3a15c930120bd45a3e20df6021f9393ab8c
Tx public key: e1bf45e3b043f7dc634981d3ed9919d94cdbb2616da65c6f46eee4f300db9bf1
Timestamp: 1766717535 Timestamp [UCT]: 2025-12-26 02:52:15 Age [y:d:h:m:s]: 00:000:11:55:28
Block: 1441727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360 RingCT/type: yes/0
Extra: 01e1bf45e3b043f7dc634981d3ed9919d94cdbb2616da65c6f46eee4f300db9bf10211000000027b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a80e1e08de8e49d221ac09013878124179a66db4c8cebaa39681c03910e338f 0.600000000000 1930622 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": 1441737, "vin": [ { "gen": { "height": 1441727 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a80e1e08de8e49d221ac09013878124179a66db4c8cebaa39681c03910e338f" } } ], "extra": [ 1, 225, 191, 69, 227, 176, 67, 247, 220, 99, 73, 129, 211, 237, 153, 25, 217, 76, 219, 178, 97, 109, 166, 92, 111, 70, 238, 228, 243, 0, 219, 155, 241, 2, 17, 0, 0, 0, 2, 123, 30, 81, 172, 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