Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3eb7402aede3d7b3fe1143b0287f7504e4e36c22a4924e7ed85331b90f18d81

Tx prefix hash: f8c807613a7d55949c333199868f6b7ad1bf0181a4daaa61dac01834bfa7ef7c
Tx public key: 3b0e95bd77243c13ef808e9d802712a6c8526941059f4731b30c26130e9e8e85
Timestamp: 1687426513 Timestamp [UCT]: 2023-06-22 09:35:13 Age [y:d:h:m:s]: 01:250:05:47:47
Block: 787750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439989 RingCT/type: yes/0
Extra: 013b0e95bd77243c13ef808e9d802712a6c8526941059f4731b30c26130e9e8e85021100000002faf35c9c000000000000000000

1 output(s) for total of 1.506172411000 dcy

stealth address amount amount idx
00: b1e940975380f39fa47f8542fd30ee44e3144da6f0e54798665c1548f35a7d98 1.506172411000 1237829 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": 787760, "vin": [ { "gen": { "height": 787750 } } ], "vout": [ { "amount": 1506172411, "target": { "key": "b1e940975380f39fa47f8542fd30ee44e3144da6f0e54798665c1548f35a7d98" } } ], "extra": [ 1, 59, 14, 149, 189, 119, 36, 60, 19, 239, 128, 142, 157, 128, 39, 18, 166, 200, 82, 105, 65, 5, 159, 71, 49, 179, 12, 38, 19, 14, 158, 142, 133, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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