Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 661e5501fd7ce834b6306cb9a3039cf1a759c8ea2adf90beedfc05f22af80674

Tx prefix hash: d8c9db3686f58c5d632872360b6401635199f7ddcfdfd8b9dfaccf3ae50a93bf
Tx public key: 35f5e133cb9410cc90146dce399654bf1a583f4e2850552119324f737d64a46f
Timestamp: 1736650628 Timestamp [UCT]: 2025-01-12 02:57:08 Age [y:d:h:m:s]: 00:157:09:38:08
Block: 1195447 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112210 RingCT/type: yes/0
Extra: 0135f5e133cb9410cc90146dce399654bf1a583f4e2850552119324f737d64a46f021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1d5f4a3e89d074845da4d0f19cf7e5eb2969a9bf5e05c4dec544fd2173cb80c 0.600000000000 1682038 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": 1195457, "vin": [ { "gen": { "height": 1195447 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1d5f4a3e89d074845da4d0f19cf7e5eb2969a9bf5e05c4dec544fd2173cb80c" } } ], "extra": [ 1, 53, 245, 225, 51, 203, 148, 16, 204, 144, 20, 109, 206, 57, 150, 84, 191, 26, 88, 63, 78, 40, 80, 85, 33, 25, 50, 79, 115, 125, 100, 164, 111, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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