Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a25774e551ad918e407dcee819ebd1806b53a910f0c5590e9beaef24b57eb97

Tx prefix hash: 8d5ba5ce8e4c7f6bdc0ea518e6d32cfd68eb578e9ab50b53ee9434019f9b94a8
Tx public key: 33c11d20d7edf87235bfd6e441a0f8b17d7d0bd2532836a871deb1e9fa09ab86
Timestamp: 1699103937 Timestamp [UCT]: 2023-11-04 13:18:57 Age [y:d:h:m:s]: 02:004:12:48:28
Block: 884562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 522774 RingCT/type: yes/0
Extra: 0133c11d20d7edf87235bfd6e441a0f8b17d7d0bd2532836a871deb1e9fa09ab8602110000000775e3f0e9000000000000000000

1 output(s) for total of 0.719579696000 dcy

stealth address amount amount idx
00: a96b58d169a2d0ee142f6ec47d4db2f0e3e99d67b5f7dfae38351d9bb51f6d81 0.719579696000 1340307 of 0

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": 884572, "vin": [ { "gen": { "height": 884562 } } ], "vout": [ { "amount": 719579696, "target": { "key": "a96b58d169a2d0ee142f6ec47d4db2f0e3e99d67b5f7dfae38351d9bb51f6d81" } } ], "extra": [ 1, 51, 193, 29, 32, 215, 237, 248, 114, 53, 191, 214, 228, 65, 160, 248, 177, 125, 125, 11, 210, 83, 40, 54, 168, 113, 222, 177, 233, 250, 9, 171, 134, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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