Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ea3c390eef5e553234ff89e56785662281ad81a4a89a813cdee56253b41b3c6

Tx prefix hash: 741ebdf9b0e4d842b7456612193db35f3a3e94f3a5fe957998293ad280fe1d84
Tx public key: 8b6f9c180b77ae7acbdfa25a11660b9f49da71e1a3dfc3bbe1a86f0d41679749
Timestamp: 1707659278 Timestamp [UCT]: 2024-02-11 13:47:58 Age [y:d:h:m:s]: 00:221:02:36:39
Block: 955231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158394 RingCT/type: yes/0
Extra: 018b6f9c180b77ae7acbdfa25a11660b9f49da71e1a3dfc3bbe1a86f0d4167974902110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 673a13ad4f4022e075b52d7cade0fa90046adb8062297e01973c10694caa0dbc 0.600000000000 1414517 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": 955241, "vin": [ { "gen": { "height": 955231 } } ], "vout": [ { "amount": 600000000, "target": { "key": "673a13ad4f4022e075b52d7cade0fa90046adb8062297e01973c10694caa0dbc" } } ], "extra": [ 1, 139, 111, 156, 24, 11, 119, 174, 122, 203, 223, 162, 90, 17, 102, 11, 159, 73, 218, 113, 225, 163, 223, 195, 187, 225, 168, 111, 13, 65, 103, 151, 73, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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