Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc96d98dd12b231237ec2852a59584254cadaf95dcab32520d6b8b8bfe8aecef

Tx prefix hash: d0ee6efd411a304bc23fa12d19a8c4dd5c89874e15bbcfa6c722152a79467c6f
Tx public key: bf034bd9b9477a5af8440e3b333ea0ccd4a30c8c722966c5ce3b7327509f2869
Timestamp: 1583240551 Timestamp [UCT]: 2020-03-03 13:02:31 Age [y:d:h:m:s]: 04:297:13:13:11
Block: 75845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106730 RingCT/type: yes/0
Extra: 01bf034bd9b9477a5af8440e3b333ea0ccd4a30c8c722966c5ce3b7327509f28690211000000134943cd9f000000000000000000

1 output(s) for total of 344.108045034000 dcy

stealth address amount amount idx
00: b617eb57a2099dbed168b7976896b412f2aa05d77187217dd004e1487130ffbf 344.108045034000 139824 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": 75855, "vin": [ { "gen": { "height": 75845 } } ], "vout": [ { "amount": 344108045034, "target": { "key": "b617eb57a2099dbed168b7976896b412f2aa05d77187217dd004e1487130ffbf" } } ], "extra": [ 1, 191, 3, 75, 217, 185, 71, 122, 90, 248, 68, 14, 59, 51, 62, 160, 204, 212, 163, 12, 140, 114, 41, 102, 197, 206, 59, 115, 39, 80, 159, 40, 105, 2, 17, 0, 0, 0, 19, 73, 67, 205, 159, 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