Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eda264379634bb0acbc053ded74ea3c1991b02cd7ab9e0f3e778f4bdf6a8d73c

Tx prefix hash: 6fdec26c06cdf006150614a2a37f8e9680e9a104a17f9e336b4f2f8e680949da
Tx public key: fd1ed290750c36b860f7539277fe8d4d8191a3cb813b77773e72b0683dabbe5a
Timestamp: 1722950411 Timestamp [UCT]: 2024-08-06 13:20:11 Age [y:d:h:m:s]: 00:295:08:39:36
Block: 1082012 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211029 RingCT/type: yes/0
Extra: 01fd1ed290750c36b860f7539277fe8d4d8191a3cb813b77773e72b0683dabbe5a021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6cede96df3732d579f6cd3f315a2597076c87e8ad51b49f3f5a89ec38cf1a740 0.600000000000 1555835 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": 1082022, "vin": [ { "gen": { "height": 1082012 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cede96df3732d579f6cd3f315a2597076c87e8ad51b49f3f5a89ec38cf1a740" } } ], "extra": [ 1, 253, 30, 210, 144, 117, 12, 54, 184, 96, 247, 83, 146, 119, 254, 141, 77, 129, 145, 163, 203, 129, 59, 119, 119, 62, 114, 176, 104, 61, 171, 190, 90, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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