Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c6a9d42149de23ac69490a607bc41b1f2368f77ea394ceaf077d3ecf3443570

Tx prefix hash: dd0ca69f5f6b5df1f65557d2f253ce22ec967d41ca62c0faef694eebbe4082e4
Tx public key: 670b5498d5c9bbb2139fd30946a8236d92df82831413164783a1f28ac80e9a0d
Timestamp: 1755287886 Timestamp [UCT]: 2025-08-15 19:58:06 Age [y:d:h:m:s]: 00:010:00:25:27
Block: 1347400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6956 RingCT/type: yes/0
Extra: 01670b5498d5c9bbb2139fd30946a8236d92df82831413164783a1f28ac80e9a0d021100000005b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d85bb5cfeb823f0f649583abec3f81bdb0cdb8e04770a5231efb149e36baa64a 0.600000000000 1835317 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": 1347410, "vin": [ { "gen": { "height": 1347400 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d85bb5cfeb823f0f649583abec3f81bdb0cdb8e04770a5231efb149e36baa64a" } } ], "extra": [ 1, 103, 11, 84, 152, 213, 201, 187, 178, 19, 159, 211, 9, 70, 168, 35, 109, 146, 223, 130, 131, 20, 19, 22, 71, 131, 161, 242, 138, 200, 14, 154, 13, 2, 17, 0, 0, 0, 5, 178, 247, 132, 196, 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