Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4556a54fa08fb2a4fc91b3fb4a82a98b995d7907c225d4f41ff29465466f3f07

Tx prefix hash: 07fd9e44c7c769b9ec989d908f14bd1dfb876a83c43a8a3d768322f6791ef186
Tx public key: 443a1a28209f01c21cbb02b1d18022db754d2d87e2895b6f6dc71c84123384dc
Timestamp: 1696972127 Timestamp [UCT]: 2023-10-10 21:08:47 Age [y:d:h:m:s]: 01:225:14:35:29
Block: 866855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 422305 RingCT/type: yes/0
Extra: 01443a1a28209f01c21cbb02b1d18022db754d2d87e2895b6f6dc71c84123384dc021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.823663021000 dcy

stealth address amount amount idx
00: 0c222f6f02b8f016917814309c5caa941200389d6d1c9203e65e87ba489455da 0.823663021000 1321493 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": 866865, "vin": [ { "gen": { "height": 866855 } } ], "vout": [ { "amount": 823663021, "target": { "key": "0c222f6f02b8f016917814309c5caa941200389d6d1c9203e65e87ba489455da" } } ], "extra": [ 1, 68, 58, 26, 40, 32, 159, 1, 194, 28, 187, 2, 177, 209, 128, 34, 219, 117, 77, 45, 135, 226, 137, 91, 111, 109, 199, 28, 132, 18, 51, 132, 220, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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