Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9d76b7ef0e1d4a057e34e8cf80c43d4d0343381b1a8ab0eb7e646761942c89e

Tx prefix hash: efa251c0ef7270eb7b20ab2f406d4cd04f22bf75893335caa0c48eda90af1993
Tx public key: 9d95159059d28f5c30531e2dd60acad514f821a3473f3e8ec366be0ab0faffd4
Timestamp: 1729557614 Timestamp [UCT]: 2024-10-22 00:40:14 Age [y:d:h:m:s]: 00:093:02:52:56
Block: 1136753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66547 RingCT/type: yes/0
Extra: 019d95159059d28f5c30531e2dd60acad514f821a3473f3e8ec366be0ab0faffd4021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 416366b6d6c5a31cde26fbb6e6d125a04acbcb2072d3e850a8b64c3fb20ca911 0.600000000000 1620118 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": 1136763, "vin": [ { "gen": { "height": 1136753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "416366b6d6c5a31cde26fbb6e6d125a04acbcb2072d3e850a8b64c3fb20ca911" } } ], "extra": [ 1, 157, 149, 21, 144, 89, 210, 143, 92, 48, 83, 30, 45, 214, 10, 202, 213, 20, 248, 33, 163, 71, 63, 62, 142, 195, 102, 190, 10, 176, 250, 255, 212, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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