Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7085595a34f6887e2b6b45d4f2955b3c124d1f808752912cca1380f378629dcc

Tx prefix hash: 69040d54eac214dd9147f96c6dd0b5b953bc6575829aa4812e9090da3b94f59d
Tx public key: 3716c7bca0c7d837a66d0cfbceab0c5787dbd639552286eb2a181d27fda54cc9
Timestamp: 1717340499 Timestamp [UCT]: 2024-06-02 15:01:39 Age [y:d:h:m:s]: 01:164:17:50:47
Block: 1035513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376327 RingCT/type: yes/0
Extra: 013716c7bca0c7d837a66d0cfbceab0c5787dbd639552286eb2a181d27fda54cc902110000000241ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b370b9f229bde0ac3ae89f35bb0f234529de874fce301ce474cfbf7994dddc4f 0.600000000000 1504034 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": 1035523, "vin": [ { "gen": { "height": 1035513 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b370b9f229bde0ac3ae89f35bb0f234529de874fce301ce474cfbf7994dddc4f" } } ], "extra": [ 1, 55, 22, 199, 188, 160, 199, 216, 55, 166, 109, 12, 251, 206, 171, 12, 87, 135, 219, 214, 57, 85, 34, 134, 235, 42, 24, 29, 39, 253, 165, 76, 201, 2, 17, 0, 0, 0, 2, 65, 238, 28, 155, 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