Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c7f6803335309fea4faa38eec7bc30626938c16b8f1f6f37226b1f86cd5e9e9

Tx prefix hash: 92e8321f16f79caf6cf4d4f095b04b96dec32697e9a8896f37faab78fb853f53
Tx public key: 1d389302ef4ff3e4d4454b25ed572fd97afab881d1e70926246a043cf68916c3
Timestamp: 1755371860 Timestamp [UCT]: 2025-08-16 19:17:40 Age [y:d:h:m:s]: 00:094:03:53:54
Block: 1348006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67117 RingCT/type: yes/0
Extra: 011d389302ef4ff3e4d4454b25ed572fd97afab881d1e70926246a043cf68916c3021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38281b15111a28c917229be3cd2f5a576b4bdb390f7576318d869141c0d34e1a 0.600000000000 1835929 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": 1348016, "vin": [ { "gen": { "height": 1348006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38281b15111a28c917229be3cd2f5a576b4bdb390f7576318d869141c0d34e1a" } } ], "extra": [ 1, 29, 56, 147, 2, 239, 79, 243, 228, 212, 69, 75, 37, 237, 87, 47, 217, 122, 250, 184, 129, 209, 231, 9, 38, 36, 106, 4, 60, 246, 137, 22, 195, 2, 17, 0, 0, 0, 2, 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