Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8b22b302d70e5ae251af60645a16229e82116e959b2f4ca56d060573ea22a8b

Tx prefix hash: b296e6864a360bee01535ceb6ac941d8e873a5426a757ff87c5189a6cd12e3df
Tx public key: bec9ce5fcd5cd38a41c83383b634fe39ea736d56a2c8d91c1099831dad736295
Timestamp: 1686437697 Timestamp [UCT]: 2023-06-10 22:54:57 Age [y:d:h:m:s]: 01:362:09:16:06
Block: 779568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 520216 RingCT/type: yes/0
Extra: 01bec9ce5fcd5cd38a41c83383b634fe39ea736d56a2c8d91c1099831dad7362950211000000024b8f5122000000000000000000

1 output(s) for total of 1.603126384000 dcy

stealth address amount amount idx
00: f3f85b2681a7d0861231b30aee7f6aa0a577168b1c6bce2a5ac8556d32dd1e60 1.603126384000 1229231 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": 779578, "vin": [ { "gen": { "height": 779568 } } ], "vout": [ { "amount": 1603126384, "target": { "key": "f3f85b2681a7d0861231b30aee7f6aa0a577168b1c6bce2a5ac8556d32dd1e60" } } ], "extra": [ 1, 190, 201, 206, 95, 205, 92, 211, 138, 65, 200, 51, 131, 182, 52, 254, 57, 234, 115, 109, 86, 162, 200, 217, 28, 16, 153, 131, 29, 173, 115, 98, 149, 2, 17, 0, 0, 0, 2, 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