Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8d6823444e297e6df491dd1d0e55acd363ba70c69876a12526a1e7a0083e238

Tx prefix hash: fe2c67540419ff73a9e1bf899e65f47311c27a4e3fb38998af91afc3a5b73ff6
Tx public key: bdad1c3c56e34b970b6dc714c494c83eda264e33f57449eff72a6a3be4525d1e
Timestamp: 1707642309 Timestamp [UCT]: 2024-02-11 09:05:09 Age [y:d:h:m:s]: 00:354:08:57:50
Block: 955093 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253424 RingCT/type: yes/0
Extra: 01bdad1c3c56e34b970b6dc714c494c83eda264e33f57449eff72a6a3be4525d1e0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3bb0288d9fc45f5a0ef32ab3c008ed1bf9d3b8cbf3af966a88572e17aadda6d6 0.600000000000 1414375 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": 955103, "vin": [ { "gen": { "height": 955093 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bb0288d9fc45f5a0ef32ab3c008ed1bf9d3b8cbf3af966a88572e17aadda6d6" } } ], "extra": [ 1, 189, 173, 28, 60, 86, 227, 75, 151, 11, 109, 199, 20, 196, 148, 200, 62, 218, 38, 78, 51, 245, 116, 73, 239, 247, 42, 106, 59, 228, 82, 93, 30, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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