Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95df7d765da81f6f8952895085306a163e978f8623648ef726f0ffa9b3fe32bc

Tx prefix hash: 55c9cdae1fab64fdc746056d46e5238e884b533d1c3581f6763b0d317e1fe4ad
Tx public key: ce8a89aaa7005b3d38f0b2f1506e480fb06493b7553ed1e1e51dc69129df4110
Timestamp: 1706456382 Timestamp [UCT]: 2024-01-28 15:39:42 Age [y:d:h:m:s]: 01:312:03:16:39
Block: 945245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 481920 RingCT/type: yes/0
Extra: 01ce8a89aaa7005b3d38f0b2f1506e480fb06493b7553ed1e1e51dc69129df411002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d370ffc285ba9c7929b051ce551f7df69213bf357c5a898bf5bf21fed6f7fcf1 0.600000000000 1403555 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": 945255, "vin": [ { "gen": { "height": 945245 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d370ffc285ba9c7929b051ce551f7df69213bf357c5a898bf5bf21fed6f7fcf1" } } ], "extra": [ 1, 206, 138, 137, 170, 167, 0, 91, 61, 56, 240, 178, 241, 80, 110, 72, 15, 176, 100, 147, 183, 85, 62, 209, 225, 229, 29, 198, 145, 41, 223, 65, 16, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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