Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cacc5ddc4596931ace8f71b3cfc256849a278340001581863c586fbc18acda2

Tx prefix hash: c73fc9c576d9c6543b320bf65ddcf44bc82bbfabc9413ecd679e0dd4cc7f34fb
Tx public key: 54a25cde9290a6f1f1f4f8cc86c3279f2097554e2fded90e407a095433e1f5e9
Timestamp: 1731255844 Timestamp [UCT]: 2024-11-10 16:24:04 Age [y:d:h:m:s]: 00:013:21:17:27
Block: 1150785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9937 RingCT/type: yes/0
Extra: 0154a25cde9290a6f1f1f4f8cc86c3279f2097554e2fded90e407a095433e1f5e90211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de8ffb0e1b5051bf7ae3dcd219253196a410d4dd3e433a36a5e262a09404313b 0.600000000000 1636182 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": 1150795, "vin": [ { "gen": { "height": 1150785 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de8ffb0e1b5051bf7ae3dcd219253196a410d4dd3e433a36a5e262a09404313b" } } ], "extra": [ 1, 84, 162, 92, 222, 146, 144, 166, 241, 241, 244, 248, 204, 134, 195, 39, 159, 32, 151, 85, 78, 47, 222, 217, 14, 64, 122, 9, 84, 51, 225, 245, 233, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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