Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aeb204cd9ec0a5ebc37f6d5bfa3256bc8f405166700618c6f4ce6834a2c911db

Tx prefix hash: 1703da99fed90857c23521139c75e782580fa4092e43f6c33df4db48c60085b2
Tx public key: e0a6d8f5e69fb4dcf6152abab64b595c2c3f3793a3ee9b6abd2be731d7a7154b
Timestamp: 1700927972 Timestamp [UCT]: 2023-11-25 15:59:32 Age [y:d:h:m:s]: 01:361:08:26:48
Block: 899437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 517145 RingCT/type: yes/0
Extra: 01e0a6d8f5e69fb4dcf6152abab64b595c2c3f3793a3ee9b6abd2be731d7a7154b02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.642379731000 dcy

stealth address amount amount idx
00: 0781e27a61644a016257d7957ae8741b788cbfdf944da396bab995b0fac118d2 0.642379731000 1355892 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": 899447, "vin": [ { "gen": { "height": 899437 } } ], "vout": [ { "amount": 642379731, "target": { "key": "0781e27a61644a016257d7957ae8741b788cbfdf944da396bab995b0fac118d2" } } ], "extra": [ 1, 224, 166, 216, 245, 230, 159, 180, 220, 246, 21, 42, 186, 182, 75, 89, 92, 44, 63, 55, 147, 163, 238, 155, 106, 189, 43, 231, 49, 215, 167, 21, 75, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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