Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06a589e1eb3908e5bfc85c7fff0929866ba009f42dac2574886a274c9ac9232a

Tx prefix hash: a5a7246f9cd95601215679e68d5705cf9c0759efd1b9891d01a36461d63e90e0
Tx public key: 0f05fabc85018aa384456f4cdbcc7942b8d2a5af5627df9015a629b8e34f8ca9
Timestamp: 1735157680 Timestamp [UCT]: 2024-12-25 20:14:40 Age [y:d:h:m:s]: 00:172:09:44:41
Block: 1183102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122949 RingCT/type: yes/0
Extra: 010f05fabc85018aa384456f4cdbcc7942b8d2a5af5627df9015a629b8e34f8ca90211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7d44ecb4b4edd01d8528c4fdd791598504be8d2065f5a7d575ced1e889e15bf 0.600000000000 1669543 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": 1183112, "vin": [ { "gen": { "height": 1183102 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7d44ecb4b4edd01d8528c4fdd791598504be8d2065f5a7d575ced1e889e15bf" } } ], "extra": [ 1, 15, 5, 250, 188, 133, 1, 138, 163, 132, 69, 111, 76, 219, 204, 121, 66, 184, 210, 165, 175, 86, 39, 223, 144, 21, 166, 41, 184, 227, 79, 140, 169, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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