Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b35da29e22bbc9ce0dfb55b9192fd671fc353f1d9abd694ad9ee84d0143ff9e

Tx prefix hash: 38257754a37bbf06f0fafcf5d14ef4e694a83788debf54d2c92f38a91a387430
Tx public key: cfba9e2698d225a405c20df7b46e99d1f44eb5d672a6f0c1f07e1bd1209ec103
Timestamp: 1734148183 Timestamp [UCT]: 2024-12-14 03:49:43 Age [y:d:h:m:s]: 00:113:17:55:17
Block: 1174758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81057 RingCT/type: yes/0
Extra: 01cfba9e2698d225a405c20df7b46e99d1f44eb5d672a6f0c1f07e1bd1209ec103021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f18d59cce4a01165f7d8ccfdfc3470d6d7e5fb974f27624a2a618db4558a577 0.600000000000 1660951 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": 1174768, "vin": [ { "gen": { "height": 1174758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f18d59cce4a01165f7d8ccfdfc3470d6d7e5fb974f27624a2a618db4558a577" } } ], "extra": [ 1, 207, 186, 158, 38, 152, 210, 37, 164, 5, 194, 13, 247, 180, 110, 153, 209, 244, 78, 181, 214, 114, 166, 240, 193, 240, 126, 27, 209, 32, 158, 193, 3, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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