Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4dddc22286f24d7c83ec1e079e393a62d6ba74eb13f4db01647db19c46d325fb

Tx prefix hash: c1716d85e167f4603e3ec60b16b5c9b778c5bd240ce18e897d13f8399fa2215d
Tx public key: a75311100d92a2341e658c1fd15e7faa8ddae91fb6515e099a871af9da5ce614
Timestamp: 1717648707 Timestamp [UCT]: 2024-06-06 04:38:27 Age [y:d:h:m:s]: 00:232:20:03:50
Block: 1038063 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166587 RingCT/type: yes/0
Extra: 01a75311100d92a2341e658c1fd15e7faa8ddae91fb6515e099a871af9da5ce6140211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f7e56813c43c716e9e65faf6cfbc57114ef3e3d978bbc77472b13239bce6fbf 0.600000000000 1506622 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": 1038073, "vin": [ { "gen": { "height": 1038063 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f7e56813c43c716e9e65faf6cfbc57114ef3e3d978bbc77472b13239bce6fbf" } } ], "extra": [ 1, 167, 83, 17, 16, 13, 146, 162, 52, 30, 101, 140, 31, 209, 94, 127, 170, 141, 218, 233, 31, 182, 81, 94, 9, 154, 135, 26, 249, 218, 92, 230, 20, 2, 17, 0, 0, 0, 3, 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