Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35871a4ea85e541c76a24380433c823f5ae151098fbeb3c90149f9c8e5c032f1

Tx prefix hash: 42f2bdb8ac4efddea90e0462c3dd41ffbfd9bbcfeaa29d4ebc3270b404962cab
Tx public key: a183a658696831fc1e53b7629bc8da742a605dd3b55c85445e3cb43060146387
Timestamp: 1724156284 Timestamp [UCT]: 2024-08-20 12:18:04 Age [y:d:h:m:s]: 00:221:02:50:38
Block: 1092022 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157890 RingCT/type: yes/0
Extra: 01a183a658696831fc1e53b7629bc8da742a605dd3b55c85445e3cb43060146387021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3ae76a4bd78d3200c864181a3e5ab8a80f9f251e915a3fbe6a9b498ae7c2797 0.600000000000 1566681 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": 1092032, "vin": [ { "gen": { "height": 1092022 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3ae76a4bd78d3200c864181a3e5ab8a80f9f251e915a3fbe6a9b498ae7c2797" } } ], "extra": [ 1, 161, 131, 166, 88, 105, 104, 49, 252, 30, 83, 183, 98, 155, 200, 218, 116, 42, 96, 93, 211, 181, 92, 133, 68, 94, 60, 180, 48, 96, 20, 99, 135, 2, 17, 0, 0, 0, 5, 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