Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0323c84482bc14e24402d3ab6040e845b95625503a3269057c38033e46a03acf

Tx prefix hash: 44880f2f8580b78ca2a0a3a676fcabf7a58b26481cda20b886836736d97d323b
Tx public key: 74017b949b467217c1ada52764aaf04a63ffe7539e7d5a0d43a2f9dfa5dbfd1f
Timestamp: 1696118120 Timestamp [UCT]: 2023-09-30 23:55:20 Age [y:d:h:m:s]: 01:240:13:10:29
Block: 859765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433019 RingCT/type: yes/0
Extra: 0174017b949b467217c1ada52764aaf04a63ffe7539e7d5a0d43a2f9dfa5dbfd1f0211000000074b8f5122000000000000000000

1 output(s) for total of 0.869444154000 dcy

stealth address amount amount idx
00: d6907bd1347d2daef3607a5fd12fc501d3252bba6f784207a67ee5362c2fb17f 0.869444154000 1314011 of 0

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": 859775, "vin": [ { "gen": { "height": 859765 } } ], "vout": [ { "amount": 869444154, "target": { "key": "d6907bd1347d2daef3607a5fd12fc501d3252bba6f784207a67ee5362c2fb17f" } } ], "extra": [ 1, 116, 1, 123, 148, 155, 70, 114, 23, 193, 173, 165, 39, 100, 170, 240, 74, 99, 255, 231, 83, 158, 125, 90, 13, 67, 162, 249, 223, 165, 219, 253, 31, 2, 17, 0, 0, 0, 7, 75, 143, 81, 34, 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