Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a806cd1f8f6f7e624e25e8c98e34628adf72d9ade778705c5f11ac5b4664c981

Tx prefix hash: d64fcf9126f10085b37f8c83e8fe483d2563ae6aefe103308d18e54c79be7baf
Tx public key: 5f41cfb0a8a9cca2900193970f0ddd7dbe2ab6330e9cdce5f75da67e116ab5ce
Timestamp: 1628690766 Timestamp [UCT]: 2021-08-11 14:06:06 Age [y:d:h:m:s]: 04:085:20:17:40
Block: 311812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1092909 RingCT/type: yes/0
Extra: 015f41cfb0a8a9cca2900193970f0ddd7dbe2ab6330e9cdce5f75da67e116ab5ce02110000001b01f1e57f000000000000000000

1 output(s) for total of 56.864061767000 dcy

stealth address amount amount idx
00: 9c596fe62afcac5f6ff1b82c1dc46987b833e8aacc05ea68d7d42930e32930c1 56.864061767000 648877 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": 311822, "vin": [ { "gen": { "height": 311812 } } ], "vout": [ { "amount": 56864061767, "target": { "key": "9c596fe62afcac5f6ff1b82c1dc46987b833e8aacc05ea68d7d42930e32930c1" } } ], "extra": [ 1, 95, 65, 207, 176, 168, 169, 204, 162, 144, 1, 147, 151, 15, 13, 221, 125, 190, 42, 182, 51, 14, 156, 220, 229, 247, 93, 166, 126, 17, 106, 181, 206, 2, 17, 0, 0, 0, 27, 1, 241, 229, 127, 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