Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38c8e324415ec0c62223f4336f7ae18fa0abf033a2d86d6ca5de01db9694421a

Tx prefix hash: 2f9d9b1ce9b1a42df6e4b759aa40bc50d8338c122d48de30902b198acb4a9e07
Tx public key: 2dde3b3de0cd8e813286e9bf8d193695bc2492f4174849210d321d002e68d875
Timestamp: 1710064894 Timestamp [UCT]: 2024-03-10 10:01:34 Age [y:d:h:m:s]: 01:094:04:46:08
Block: 975203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328308 RingCT/type: yes/0
Extra: 012dde3b3de0cd8e813286e9bf8d193695bc2492f4174849210d321d002e68d87502110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a7f64f3825289f666b94642765eba7dc7cab02de84b16e3aecf03f5f76fd5b9 0.600000000000 1435174 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": 975213, "vin": [ { "gen": { "height": 975203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a7f64f3825289f666b94642765eba7dc7cab02de84b16e3aecf03f5f76fd5b9" } } ], "extra": [ 1, 45, 222, 59, 61, 224, 205, 142, 129, 50, 134, 233, 191, 141, 25, 54, 149, 188, 36, 146, 244, 23, 72, 73, 33, 13, 50, 29, 0, 46, 104, 216, 117, 2, 17, 0, 0, 0, 4, 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