Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7c2d1a345424be0a5b3526e12c33f31db50ff39cdcb920f693497616b5884d1

Tx prefix hash: 9392df79fbffc83341b710404a74cbaebe9a3bab608b4b0676ab877c0ac90d07
Tx public key: b5e74e2d3829bd9d490720684fbb84b471d4f0441a64e1aea28977fc0d9524d3
Timestamp: 1728851263 Timestamp [UCT]: 2024-10-13 20:27:43 Age [y:d:h:m:s]: 00:160:12:58:58
Block: 1130937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114519 RingCT/type: yes/0
Extra: 01b5e74e2d3829bd9d490720684fbb84b471d4f0441a64e1aea28977fc0d9524d302110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2cbcc3a2245a3dfb3121362eda369167b79d0cc654a137a7bd7b22b093179bf 0.600000000000 1613818 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": 1130947, "vin": [ { "gen": { "height": 1130937 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2cbcc3a2245a3dfb3121362eda369167b79d0cc654a137a7bd7b22b093179bf" } } ], "extra": [ 1, 181, 231, 78, 45, 56, 41, 189, 157, 73, 7, 32, 104, 79, 187, 132, 180, 113, 212, 240, 68, 26, 100, 225, 174, 162, 137, 119, 252, 13, 149, 36, 211, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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