Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b299c01f27e671c4209667ff8b18eb627e6f1079f40f1f8837c475ef8ef9ab80

Tx prefix hash: 10c10f88b6171092ad4e6920136807ab89e2ccd51ad851f0c3b79d3aa37fe244
Tx public key: a5a4f871a83c03229d6ff48eb2e112297271803caee19b2fa193100409f0c471
Timestamp: 1695047744 Timestamp [UCT]: 2023-09-18 14:35:44 Age [y:d:h:m:s]: 02:050:10:04:44
Block: 850885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 555687 RingCT/type: yes/0
Extra: 01a5a4f871a83c03229d6ff48eb2e112297271803caee19b2fa193100409f0c47102110000000a4b8f5122000000000000000000

1 output(s) for total of 0.930389566000 dcy

stealth address amount amount idx
00: b121882fb34a378c002ea898c7a2d0964a3d4c8798e9de05d31af44bff80920b 0.930389566000 1304631 of 0

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": 850895, "vin": [ { "gen": { "height": 850885 } } ], "vout": [ { "amount": 930389566, "target": { "key": "b121882fb34a378c002ea898c7a2d0964a3d4c8798e9de05d31af44bff80920b" } } ], "extra": [ 1, 165, 164, 248, 113, 168, 60, 3, 34, 157, 111, 244, 142, 178, 225, 18, 41, 114, 113, 128, 60, 174, 225, 155, 47, 161, 147, 16, 4, 9, 240, 196, 113, 2, 17, 0, 0, 0, 10, 75, 143, 81, 34, 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