Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7f4dbda9bf83a90f5b89b22d1c3a46b3eb695f8f0168df9245bf172bc343452

Tx prefix hash: 837dbd961e4db77f85b5cba3875bb88e981c84b85dd7ec2c460ea18319c33750
Tx public key: 0caae59ce3a77dae2b3bb58763db5d597166c6e3fd2c0074d95b1dd90f97d873
Timestamp: 1704205031 Timestamp [UCT]: 2024-01-02 14:17:11 Age [y:d:h:m:s]: 01:016:15:19:30
Block: 926595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273240 RingCT/type: yes/0
Extra: 010caae59ce3a77dae2b3bb58763db5d597166c6e3fd2c0074d95b1dd90f97d87302110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b32b12d4ed5728fe6c355fdc262158d7d583a33d359509760f4577b2e9a5914c 0.600000000000 1384389 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": 926605, "vin": [ { "gen": { "height": 926595 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b32b12d4ed5728fe6c355fdc262158d7d583a33d359509760f4577b2e9a5914c" } } ], "extra": [ 1, 12, 170, 229, 156, 227, 167, 125, 174, 43, 59, 181, 135, 99, 219, 93, 89, 113, 102, 198, 227, 253, 44, 0, 116, 217, 91, 29, 217, 15, 151, 216, 115, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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