Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b75adda063eb5c0db133c274295c1fc0d826352392e0195ded464515ccf0cee0

Tx prefix hash: 69acd3e54ca7b6f47305d15897a3d2387c5ac58966b9e999327264976ca4053d
Tx public key: 456e49623190785bf0b6c9acac81aaf01759dbfc1e90f5e7c43b2e0899f50120
Timestamp: 1699847428 Timestamp [UCT]: 2023-11-13 03:50:28 Age [y:d:h:m:s]: 01:199:00:20:36
Block: 890486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403460 RingCT/type: yes/0
Extra: 01456e49623190785bf0b6c9acac81aaf01759dbfc1e90f5e7c43b2e0899f5012002110000000775e3f0e9000000000000000000

1 output(s) for total of 0.687781074000 dcy

stealth address amount amount idx
00: d0c71bd0df22905d5c940d173ef1ea75a6105c0a0fb7ce0e1ed397d7134227b2 0.687781074000 1346509 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": 890496, "vin": [ { "gen": { "height": 890486 } } ], "vout": [ { "amount": 687781074, "target": { "key": "d0c71bd0df22905d5c940d173ef1ea75a6105c0a0fb7ce0e1ed397d7134227b2" } } ], "extra": [ 1, 69, 110, 73, 98, 49, 144, 120, 91, 240, 182, 201, 172, 172, 129, 170, 240, 23, 89, 219, 252, 30, 144, 245, 231, 196, 59, 46, 8, 153, 245, 1, 32, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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