Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a67ca4d50eaaf7992ab15611ced02aa5c7a20c651b11756a078e4f1ef1e98be8

Tx prefix hash: 0abe646686bb73e7c4f8fd47881924a4a978dc63ecdc2fd36b0c44b90cc8a683
Tx public key: 904b6f475f309c050e1d032da3624837dd5b504ae4c9b3e54d3dcc6e8ad24c2f
Timestamp: 1712046877 Timestamp [UCT]: 2024-04-02 08:34:37 Age [y:d:h:m:s]: 00:363:09:53:55
Block: 991597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259844 RingCT/type: yes/0
Extra: 01904b6f475f309c050e1d032da3624837dd5b504ae4c9b3e54d3dcc6e8ad24c2f02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 690e72fa72b40e747f9505b03a90277d086df3860813cbf185a637d4b407e314 0.600000000000 1451933 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": 991607, "vin": [ { "gen": { "height": 991597 } } ], "vout": [ { "amount": 600000000, "target": { "key": "690e72fa72b40e747f9505b03a90277d086df3860813cbf185a637d4b407e314" } } ], "extra": [ 1, 144, 75, 111, 71, 95, 48, 156, 5, 14, 29, 3, 45, 163, 98, 72, 55, 221, 91, 80, 74, 228, 201, 179, 229, 77, 61, 204, 110, 138, 210, 76, 47, 2, 17, 0, 0, 0, 1, 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