Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a7a1bd907c74081a42cd73a1f35c9c2f1c536930daee19f7a69fcc46d6806b7

Tx prefix hash: bec977098d11f0acae2e7a776f37fcc9f48cf7dd12b0cb8441d0471b090dfaaf
Tx public key: 0b2172d8095f0cd59dc58613a6c6b45dbad28742dff178ef8d05388a62392f82
Timestamp: 1703411051 Timestamp [UCT]: 2023-12-24 09:44:11 Age [y:d:h:m:s]: 01:108:02:30:18
Block: 920029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338383 RingCT/type: yes/0
Extra: 010b2172d8095f0cd59dc58613a6c6b45dbad28742dff178ef8d05388a62392f82021100000001ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3dafb0f73b08c33e58b79479e7a367ca3525a328b67f04b881b573a3e3fdb25 0.600000000000 1377707 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": 920039, "vin": [ { "gen": { "height": 920029 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3dafb0f73b08c33e58b79479e7a367ca3525a328b67f04b881b573a3e3fdb25" } } ], "extra": [ 1, 11, 33, 114, 216, 9, 95, 12, 213, 157, 197, 134, 19, 166, 198, 180, 93, 186, 210, 135, 66, 223, 241, 120, 239, 141, 5, 56, 138, 98, 57, 47, 130, 2, 17, 0, 0, 0, 1, 173, 86, 148, 172, 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