Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 344deaddec1382f2528f9c9c5596b8ac294313721ea1a5b2e040709c43df88fb

Tx prefix hash: 662f35e20723d10085bafcd185c4216de7dae9b88a6f555b86978d8bf0ace6bf
Tx public key: 54db1e7c8136d4d3a79405ceda5c45ad3d8bca77b4b6838450ceb847fb30adbe
Timestamp: 1762902594 Timestamp [UCT]: 2025-11-11 23:09:54 Age [y:d:h:m:s]: 00:015:08:48:21
Block: 1410112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11007 RingCT/type: yes/0
Extra: 0154db1e7c8136d4d3a79405ceda5c45ad3d8bca77b4b6838450ceb847fb30adbe021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98d3022f65d9c300e64cc46e438c8e844f06a9f60c170f998c4f4a89932601f2 0.600000000000 1898561 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": 1410122, "vin": [ { "gen": { "height": 1410112 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98d3022f65d9c300e64cc46e438c8e844f06a9f60c170f998c4f4a89932601f2" } } ], "extra": [ 1, 84, 219, 30, 124, 129, 54, 212, 211, 167, 148, 5, 206, 218, 92, 69, 173, 61, 139, 202, 119, 180, 182, 131, 132, 80, 206, 184, 71, 251, 48, 173, 190, 2, 17, 0, 0, 0, 4, 214, 225, 157, 124, 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