Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8a5ad283276c937c133e165e13dd72f3a94743a5f44eba473ce3d1048697467

Tx prefix hash: b377873e277f049a34c726e23a374cb249a8d8bc4cb47b956ce78db2ac2ac8b1
Tx public key: 5c83f6687b499942358bf9e013424123778c7469ebe5b313f8b5184eb24d4ed4
Timestamp: 1743464388 Timestamp [UCT]: 2025-03-31 23:39:48 Age [y:d:h:m:s]: 00:232:09:58:29
Block: 1251594 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163838 RingCT/type: yes/0
Extra: 015c83f6687b499942358bf9e013424123778c7469ebe5b313f8b5184eb24d4ed40211000000024060f6d2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 517f1cca83baaeafe0248a85132991df7e5b588dfef9bf260a3b92083d0b113f 0.600000000000 1738663 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": 1251604, "vin": [ { "gen": { "height": 1251594 } } ], "vout": [ { "amount": 600000000, "target": { "key": "517f1cca83baaeafe0248a85132991df7e5b588dfef9bf260a3b92083d0b113f" } } ], "extra": [ 1, 92, 131, 246, 104, 123, 73, 153, 66, 53, 139, 249, 224, 19, 66, 65, 35, 119, 140, 116, 105, 235, 229, 179, 19, 248, 181, 24, 78, 178, 77, 78, 212, 2, 17, 0, 0, 0, 2, 64, 96, 246, 210, 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