Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f3c73d2bc3dcad77dc968277c85475cb96a97f661e1834d365b94eebd2f8307

Tx prefix hash: c1301e9337672b2f5cfb877703bb86d01e971088dc8034c1a4c55b6645d660fe
Tx public key: d10b429ae470efa7d4436f65b7305d20e4a5e83bfbda0cfe88bf61cdeb4641f1
Timestamp: 1728392846 Timestamp [UCT]: 2024-10-08 13:07:26 Age [y:d:h:m:s]: 00:051:01:49:13
Block: 1127135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36498 RingCT/type: yes/0
Extra: 01d10b429ae470efa7d4436f65b7305d20e4a5e83bfbda0cfe88bf61cdeb4641f102110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e243b750faf462d06658923d42642e346bd0785637134c8f0984dfc2d9cfbd9d 0.600000000000 1609934 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": 1127145, "vin": [ { "gen": { "height": 1127135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e243b750faf462d06658923d42642e346bd0785637134c8f0984dfc2d9cfbd9d" } } ], "extra": [ 1, 209, 11, 66, 154, 228, 112, 239, 167, 212, 67, 111, 101, 183, 48, 93, 32, 228, 165, 232, 59, 251, 218, 12, 254, 136, 191, 97, 205, 235, 70, 65, 241, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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