Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a35fedb8fd7b0e18832ba747facb099116c69e23510ba021f7a5eb173e74c4f

Tx prefix hash: c392d9223812cba7eec3837573f4187963527666bb5078cfb2175fa8512c3b74
Tx public key: 8bb94a5b38dd331c534a2619485a6ff6a1fe9e321b4b789364cc37343c7f4469
Timestamp: 1732849718 Timestamp [UCT]: 2024-11-29 03:08:38 Age [y:d:h:m:s]: 00:125:00:27:18
Block: 1163982 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89150 RingCT/type: yes/0
Extra: 018bb94a5b38dd331c534a2619485a6ff6a1fe9e321b4b789364cc37343c7f44690211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40ec89a7b741e50e42ca92b73b3bd8495b4be5391f730c8e02c43e6f58ce1ea1 0.600000000000 1649653 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": 1163992, "vin": [ { "gen": { "height": 1163982 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40ec89a7b741e50e42ca92b73b3bd8495b4be5391f730c8e02c43e6f58ce1ea1" } } ], "extra": [ 1, 139, 185, 74, 91, 56, 221, 51, 28, 83, 74, 38, 25, 72, 90, 111, 246, 161, 254, 158, 50, 27, 75, 120, 147, 100, 204, 55, 52, 60, 127, 68, 105, 2, 17, 0, 0, 0, 2, 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