Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab57753ed6fa5127ce98aa8707dcd7b97f8d9f4caf50f5bb0fab669b1996f2bb

Tx prefix hash: cb9e19f6ee53c95dca5a9b6bac91d0e84695806b2a15437ebc5f76fcb452cc00
Tx public key: c91aefa69f044bb76cd54827b148c8d4baf909fce6a320ef8603ec1e64e95a1a
Timestamp: 1721780035 Timestamp [UCT]: 2024-07-24 00:13:55 Age [y:d:h:m:s]: 00:183:09:27:12
Block: 1072307 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131168 RingCT/type: yes/0
Extra: 01c91aefa69f044bb76cd54827b148c8d4baf909fce6a320ef8603ec1e64e95a1a021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5f35e65718c1933e6cdcec3edce0a3b979cf37632c0b183f33dca618f9b27f4 0.600000000000 1544768 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": 1072317, "vin": [ { "gen": { "height": 1072307 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5f35e65718c1933e6cdcec3edce0a3b979cf37632c0b183f33dca618f9b27f4" } } ], "extra": [ 1, 201, 26, 239, 166, 159, 4, 75, 183, 108, 213, 72, 39, 177, 72, 200, 212, 186, 249, 9, 252, 230, 163, 32, 239, 134, 3, 236, 30, 100, 233, 90, 26, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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