Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b0d8f4a5733d3b20bacdc70cad53aaea6a5142b602b1e157afa3c075a914b1e

Tx prefix hash: 84871f7be10c1813d79fb2f8a1ded0632e7e84cbde45a6675365ff0a73b3b1da
Tx public key: 3cae4f988bd3a65c8a544693baa7ef05ecfea3dd222530af01b4109018e45187
Timestamp: 1705757667 Timestamp [UCT]: 2024-01-20 13:34:27 Age [y:d:h:m:s]: 01:296:11:03:56
Block: 939445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 470720 RingCT/type: yes/0
Extra: 013cae4f988bd3a65c8a544693baa7ef05ecfea3dd222530af01b4109018e4518702110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31a698c9b9c9fe70b76d1809981b369435e0b8751a4ee0480779848c286beca7 0.600000000000 1397553 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": 939455, "vin": [ { "gen": { "height": 939445 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31a698c9b9c9fe70b76d1809981b369435e0b8751a4ee0480779848c286beca7" } } ], "extra": [ 1, 60, 174, 79, 152, 139, 211, 166, 92, 138, 84, 70, 147, 186, 167, 239, 5, 236, 254, 163, 221, 34, 37, 48, 175, 1, 180, 16, 144, 24, 228, 81, 135, 2, 17, 0, 0, 0, 7, 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