Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a93704b94e56e0e5fc754db7f4a0cfdf41eae34553f0c3c78a3404e36327de60

Tx prefix hash: cf23d7b13337ffb4a4132de63d9058772e23fdf137560b6adaf2c1a71701e171
Tx public key: 0607d7591940cbd4784a386ad7e75faa1a1f51d3294c811779f1e3c82fd24bb1
Timestamp: 1696254892 Timestamp [UCT]: 2023-10-02 13:54:52 Age [y:d:h:m:s]: 01:148:22:47:12
Block: 860901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367481 RingCT/type: yes/0
Extra: 010607d7591940cbd4784a386ad7e75faa1a1f51d3294c811779f1e3c82fd24bb102110000000375e3f0e9000000000000000000

1 output(s) for total of 0.861941221000 dcy

stealth address amount amount idx
00: 65caf4a3eb6cd090ddaea2b4378d7587fedd09a227109342160e1cbc7178ec1b 0.861941221000 1315211 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": 860911, "vin": [ { "gen": { "height": 860901 } } ], "vout": [ { "amount": 861941221, "target": { "key": "65caf4a3eb6cd090ddaea2b4378d7587fedd09a227109342160e1cbc7178ec1b" } } ], "extra": [ 1, 6, 7, 215, 89, 25, 64, 203, 212, 120, 74, 56, 106, 215, 231, 95, 170, 26, 31, 81, 211, 41, 76, 129, 23, 121, 241, 227, 200, 47, 210, 75, 177, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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