Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8782824b5f5d7757bafcf75c65adf6721ba2a230c7250a284cb28bbd9e1aa10d

Tx prefix hash: 06b7c61f5db3b6563152280a788b4d2620a933f72e2b7584920fc4108f533af7
Tx public key: c9b577c733eb338e1abb6700e6ae4e2bbdf1ff3803030e3d17fbb3774eab3932
Timestamp: 1720053160 Timestamp [UCT]: 2024-07-04 00:32:40 Age [y:d:h:m:s]: 00:275:11:36:37
Block: 1057985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196854 RingCT/type: yes/0
Extra: 01c9b577c733eb338e1abb6700e6ae4e2bbdf1ff3803030e3d17fbb3774eab39320211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 985e4da7e613887b3e844309d5b3c9be15aa252ec7c8242e4f1a79680f53a339 0.600000000000 1528428 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": 1057995, "vin": [ { "gen": { "height": 1057985 } } ], "vout": [ { "amount": 600000000, "target": { "key": "985e4da7e613887b3e844309d5b3c9be15aa252ec7c8242e4f1a79680f53a339" } } ], "extra": [ 1, 201, 181, 119, 199, 51, 235, 51, 142, 26, 187, 103, 0, 230, 174, 78, 43, 189, 241, 255, 56, 3, 3, 14, 61, 23, 251, 179, 119, 78, 171, 57, 50, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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