Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a09aae777a6887ba2a656307548923020f8c821b3ab6a80b342e72d431201073

Tx prefix hash: 1d942d1f8be5c08716434f0ca787c95e906005e5ad501b07a26e22191e1d4a32
Tx public key: 84fd96a7806beb9412bf9d83c40633ba6153ba474f93311495aa5fb1c784f77b
Timestamp: 1735365973 Timestamp [UCT]: 2024-12-28 06:06:13 Age [y:d:h:m:s]: 00:103:06:35:15
Block: 1184816 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73606 RingCT/type: yes/0
Extra: 0184fd96a7806beb9412bf9d83c40633ba6153ba474f93311495aa5fb1c784f77b0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e60537973a8c3a11a4eea85f4b508a4e75581d18c9ad3a83d1efa26c0e7609e9 0.600000000000 1671275 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": 1184826, "vin": [ { "gen": { "height": 1184816 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e60537973a8c3a11a4eea85f4b508a4e75581d18c9ad3a83d1efa26c0e7609e9" } } ], "extra": [ 1, 132, 253, 150, 167, 128, 107, 235, 148, 18, 191, 157, 131, 196, 6, 51, 186, 97, 83, 186, 71, 79, 147, 49, 20, 149, 170, 95, 177, 199, 132, 247, 123, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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