Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9e77420357b3e7034c780ae317a5ce2dec4f6cbfa02fee1e47dcc6c1fe2747e

Tx prefix hash: d3aa551eea01e8d5ef653a36c6514fb0d2297b7783cf85f118b9f0ebc381a802
Tx public key: d06035da68dd5d97b04697ff59f941d15f7be311a6e7b50aa753cd8d917c8b6a
Timestamp: 1677088858 Timestamp [UCT]: 2023-02-22 18:00:58 Age [y:d:h:m:s]: 01:328:07:06:22
Block: 702683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495575 RingCT/type: yes/0
Extra: 01d06035da68dd5d97b04697ff59f941d15f7be311a6e7b50aa753cd8d917c8b6a02110000000674b6d784000000000000000000

1 output(s) for total of 2.882168934000 dcy

stealth address amount amount idx
00: 95b054379b9a35e5c538c122a2ab1cfab083a2110edf43901a43348618f5b839 2.882168934000 1146222 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": 702693, "vin": [ { "gen": { "height": 702683 } } ], "vout": [ { "amount": 2882168934, "target": { "key": "95b054379b9a35e5c538c122a2ab1cfab083a2110edf43901a43348618f5b839" } } ], "extra": [ 1, 208, 96, 53, 218, 104, 221, 93, 151, 176, 70, 151, 255, 89, 249, 65, 209, 95, 123, 227, 17, 166, 231, 181, 10, 167, 83, 205, 141, 145, 124, 139, 106, 2, 17, 0, 0, 0, 6, 116, 182, 215, 132, 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